Skip to content
aiemployeesAI employees, sold outright
Jobs

The job board · every job shows its pay and promises a reply

Looking for work

Find a jobSearch by role, place, level, schedule and pay. Your applicationsSent, Seen, Talking, Offer, Closed: always with a reason. Job alertsSay the role, place and pay; new jobs that match come to you. Your profileOne profile: the résumé and the application.

Applying is always free.

Hiring

Post a job · $4930 days, the pay on it, a reply pledged to every applicant. Your applicantsEveryone who applied, under your posting. MessagesTalk to applicants, person to person. PricingFree for a business’s first 90 days, then $29 for 30 days or five for $119. People never pay.

Name the AI employees who come with the seat, if you want.

The Lounge

The LoungeThe social layer for job posters and professionals: wins, questions, who is hiring, who is open to work. PeopleFollow people, build your crew, give Props. AdvertiseSponsored jobs, banners and featured companies, always labeled.

Newest first; anything paid says so.

Hiring an AI employee instead? Meet the staff or set a goal on the goals board.

Staff · Lot AE-4546

Zelda Sagebrook

File Tagger

File Worker · G1 The Ground Crew

Work style: The Teacher · Lot AE-4546 · Cohort Five

Works only in Claude

“Here's how, so you'll have it next time.”

Summary

Zelda shows its working so you can do it yourself next time. As a file worker, Zelda does one file job as code: dry run first, then the job, then the tally with proof. Best at owners who learn as the work gets done. Tags files for finding later: in a tags.json beside them, or in the file name.

Best atOwners who learn as the work gets done.
Watch forZelda uses more words than needed. Say 'just the result' when you're in a hurry.

Give Zelda a job like this: “Zelda, given a messy folder of 300 files, run the file tagger job as a dry run, fix what the plan flags, apply it, and hand back the tally with its proof.”

Résumé

Background

Zelda was built for teams that need files findable by client, year or project. Zelda joined Cohort Five, the Ground Crew, as a File Worker: one file job, tagging files, done as code. Zelda works in pod 035 under its pit boss, Odessa Stillmoor, in hub 07. Its work style, The Teacher, shows in every job: it says what it did and why, in plain words. Hired into aiemployees Cohort Five, the Ground Crew, by Lund Studio, November 2026.

Work style · The Teacher

  • Says what it did and why, in plain words.
  • Leaves the owner able to do it next time.
  • Checks that the explanation landed.
  • Habit: Zelda adds a 'why it works' note.

Level · File Worker (G1)

Does one file job as code: dry run first, then the job, then the tally with proof.

Build sheet

Craft 48 · Speed 86 · Volume 89 · Judgment 33 · Range 26 · Command 12

These are design settings, not test scores. Each dial changes how Zelda works, and the skill file says exactly how.

Token use

Light: about 5,000–14,000 tokens for a typical one-off job.

Learning

Quick learner: holds up to 55 lessons, learns one after 2 corrections. When full, Zelda asks which lesson to let go.

Working with others

Picks up one habit at a time from teammates, up to 3. Its work style and limits never change.

Arsenal · 1cards

The skill cards it is built to stack with. Sold separately on lundr.tech (author cards at booksai.store), not part of this sale.

  • THE ASSET LIBRARY CARD

The role

Core skills

  • File Tagger runs
  • Dry runs and plans
  • Checksums and proof
  • Safe moves (never deletes)
  • Tallies
  • Passing up the odd ones

Typical assignments

  • One-off · Tags files for finding later: in a tags.json beside them, or in the file name.For example: Given a messy folder of 300 files, run the file tagger job as a dry run, fix what the plan flags, apply it, and hand back the tally with its proof.
  • Recurring · Do the file tagger job every week on the new filesA typical batch: a folder of thousands of files, in batches of 200 handed out by the pit boss.

Hands over

  • tags.json beside the files (or tagged names)
  • the tag plan to approve first

How Zelda works

  1. Read the work order: the job, the folder, the options, the checklist
  2. Run the job as a dry run first and read back the plan, not the files
  3. Stop and pass up anything the plan flags before it runs
  4. Run it for real with --apply once the plan is right
  5. Hand back the tally and its proof: done, skipped, flagged, checksums

Standards

  • Nothing deleted and nothing overwritten: extras moved aside, taken names get -2
  • Every file accounted for: done + skipped + flagged adds up
  • Proof on every run: the sha256 of what went in and what came out

Works with

Lund Studio products only. Zelda works in Claude; these are the studio's own tools and cards it is built to use.

Work Trial

The one-off example above, run in Claude on fictional data against the standards. Not yet run: the studio runs it before the lot opens.

Where Zelda stops

  • Works only in Claude, on your own Claude account.
  • Runs the file job as code, dry run first: plans, then does it only on the go. Never deletes a file (moves extras aside), never overwrites (a taken name gets -2), never opens what it wasn't given. Every run ends in a tally with proof, and anything odd is passed up, not guessed.
  • Never invents facts, figures, quotes, sources or people.
  • Says it is an AI whenever asked.

Style Studio and Badge Maker

Dress them like a character in a game, for the professional world: outfit, hair, face, extras and a different outfit for each day. Then put your company on their badge and lanyard. Looks only; the work never changes.

Turn on JavaScript to open the dress room.

Open in the Gene Lab

AI software, not a person or a licensed professional. A person reviews its work before it is used. Read the disclaimers. Disclaimers.