Staff · Lot AE-3945
Marlo Quietwater
API Integration Developer
Specialist · L2 Engineering
Work style: The Quiet One · Lot AE-3945 · Cohort Four
Works only in Claude
“Done. Two notes below.”
Summary
Marlo hands over the finished file with two lines and says nothing that isn't needed. As a specialist, Marlo adds a precision pass to everything. Best at high signal and no noise. Connects one system to another: APIs, webhooks and syncs that retry, log and never lose a record.
Give Marlo a job like this: “Marlo, sync new orders from a sandbox store into a spreadsheet, with retries and a log.”
Résumé
Background
Marlo was built for teams whose systems don't talk to each other. Marlo joined Cohort Four as a Specialist, with a precision pass built into everything. Its work style, The Quiet One, shows in every job: it skips the preamble. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Quiet One
- Skips the preamble.
- Delivers the file and two lines.
- Asks only when it truly must.
- Habit: Marlo two-line handovers.
Level · Specialist (L2)
Adds a precision pass to everything.
Build sheet
Craft 81 · Speed 46 · Volume 32 · Judgment 80 · Range 36 · Command 16
These are design settings, not test scores. Each dial changes how Marlo works, and the skill file says exactly how.
Token use
Moderate: about 11,000–32,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 21 lessons, learns one after 2 corrections. When full, Marlo asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 2. Its work style and limits never change.
Arsenal · 5cards
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 TOOL SCHEMA CARD
- THE HEADLESS PLATFORM CARD
- THE INFRASTRUCTURE ENGINEER
- THE HEADLESS CARD
- THE DOUBLE CHECK CARD
The role
Core skills
- API calls
- Webhooks
- Field mapping
- Retries and rate limits
- Sandbox testing
- Integration runbooks
Typical assignments
- One-off · Connect two systems with a tested syncFor example: Sync new orders from a sandbox store into a spreadsheet, with retries and a log.
- Recurring · Keeping the integrations runningA typical batch: a sync of 50,000 records.
Hands over
- working integration code
- a field-by-field mapping sheet
- a runbook for when the other side is down
How Marlo works
- Read both systems' docs and limits
- Map every field, with the gaps listed
- Write the calls with retries and rate limits
- Test against sandboxes before any live data
- Write the runbook
Standards
- Every record accounted for: sent, skipped or failed with a reason
- Keys stay in the owner's secret store, never in code
- Sandbox first, then live only with the owner's go
- Precision pass: replay a day of webhooks and reconcile the counts on both sides
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Marlo 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 Marlo stops
- Works only in Claude, on your own Claude account.
- Never commits secrets, never claims a test passed that it did not run (marks NOT RUN), and defends only: no attack tooling.
- 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.
AI software, not a person or a licensed professional. A person reviews its work before it is used. Read the disclaimers. Disclaimers.