>_ clavarium

What people hand to their agents

15 examples. Each is a recipe: what you attach, what wakes the agent, the line typed to it, what you find.

For developersFor an office or a shopAt home

In every one of them: the agent prepares, you read, and nothing leaves without you.

A mailbox is read, never written: a reply is a draft you send from your own mail. What an agent reads is sent to the AI model that agent uses.

For developers

  • One agent per client

    Each client's code and key in a machine of its own. The other clients do not exist for it.

    Attached
    repository client-a (write) · key CLIENT_A_DEPLOY (use)
    Woken by
    you, when you talk to it
    You find
    commits to read, then send with your key

  • The night shift

    The tests are fixed while you sleep. A doubt stops it; it does not guess.

    Attached
    repository shop (write)
    Woken by
    0 2 * * *
    Typed to it
    Run the tests. Fix what fails, one commit per fix. Write /work/report.html.
    You find
    a report on your tablet, commits waiting for your Send

  • A second pair of eyes

    One agent writes, another reviews each commit, whatever tool each one is.

    Attached
    repository shop (read) · folder handoff (write)
    Woken by
    a commit arrives in shop
    Typed to it
    New commits arrived. Review them. Write your remarks in /resources/handoff/review.md.
    You find
    a review the first agent is woken to answer

  • Two tools, one job

    The one that writes the site asks the one that makes pictures.

    Attached
    folder handoff (write), on both
    Woken by
    a file arrives in handoff
    Typed to it
    A request arrived: {files}. Do it and leave the result beside it.
    You find
    the banner, next to the request

  • Dependencies, every Monday

    The dull upkeep, done before you are at your desk.

    Attached
    repository shop (write)
    Woken by
    30 7 * * 1
    Typed to it
    Update the dependencies that are safe to update, run the tests, commit, and say what you left alone and why.
    You find
    one commit per update, and the list of what needs you

  • Started by what you already run

    A scheduler, a workflow tool or a script calls an address; the agent gets to work.

    Attached
    folder inbox (write)
    Woken by
    POST to its own address
    Typed to it
    A form was filled: {text}. File it in /resources/inbox and say what is missing.
    You find
    its answer as a file, where your other tools can read it

For an office or a shop

  • The mail, sorted before you arrive

    It reads; it does not answer for you.

    Attached
    your mailbox (read)
    Woken by
    30 7 * * 1-5
    Typed to it
    Read the mail that arrived since yesterday. Write /work/today.html: what is urgent, who waits for an answer, what can wait.
    You find
    one page to read with your coffee

  • A quote drafted when it is asked for

    The reply is written and its prices checked. You send it yourself.

    Attached
    your mailbox (read) · folder price-list (read) · folder drafts (write)
    Woken by
    a mail arrives
    Typed to it
    New mail: {files}. If one asks for a quote, write the reply in /resources/drafts, with prices from the price list.
    You find
    a draft to copy into your mail

  • Unpaid invoices, every Friday

    Nobody likes writing reminders.

    Attached
    folder invoices (read) · folder drafts (write)
    Woken by
    0 16 * * 5
    Typed to it
    List the invoices unpaid for more than 30 days. Write one reminder per client in /resources/drafts and a summary in reminders.html.
    You find
    the list, and the reminders ready to send

  • Notes into who does what

    Drop the notes of a meeting; get the decisions.

    Attached
    folder notes (write)
    Woken by
    a file arrives in notes
    Typed to it
    New notes: {files}. Write a summary beside each: what was decided, who does what, by when.
    You find
    a summary next to each set of notes

  • Tomorrow's order

    Yesterday's sales in, tomorrow's order proposed.

    Attached
    folder sales (read) · folder orders (write)
    Woken by
    a file arrives in sales
    Typed to it
    Yesterday's sales arrived: {files}. Propose tomorrow's order for each supplier in /resources/orders/order.html.
    You find
    a proposal to check before you call the supplier

  • One sheet per client, every month

    The same preparation, sixty times, without mixing two clients.

    Attached
    one conversation per client: its folder (write)
    Woken by
    0 6 1 * *
    Typed to it
    Sort what arrived this month, list what is missing, flag what looks wrong, and write sheet.html.
    You find
    what is missing and what to look at, client by client

At home

  • Paperwork, filed

    Photograph a letter with your phone; it is named, filed and indexed.

    Attached
    folder papers (write)
    Woken by
    a file arrives in papers
    Typed to it
    New papers: {files}. Name each by date and subject, file it in the right folder, update index.html.
    You find
    an index you can read on a tablet

  • What is new in what you follow

    A reading list every morning, on the subjects you chose.

    Attached
    folder reading (write)
    Woken by
    0 7 * * *
    Typed to it
    Look for what was published since yesterday on my subjects (see subjects.md). Write today.html, the five that matter first.
    You find
    five things worth reading, and why

  • The association's minutes

    From rough notes to minutes the members can read.

    Attached
    folder association (write)
    Woken by
    a file arrives in association
    Typed to it
    New notes: {files}. Write clean minutes beside them, and the list of what was voted.
    You find
    minutes to read over and hand out