agentleFS
cubexteamcubexteam/claude-sandbox-env/skills/examples/file-form/SKILL.md

file-form

Skill1 starsChanged 7 months agoMITView on GitHub

Handle small bureaucratic tasks — jury duty responses, parking tickets, passport renewals, DMV forms, permit applications, and other government or administrative paperwork.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ask what I need to get done via ask_user_input_v0.

    line 12
  2. Distinctive:

    If I share a photo of a letter or document, extract the key details: agency, deadline, case/reference number, what's being asked of me, and …

    line 22
  3. Distinctive:

    If by phone: Place the call, navigate IVR menus, and handle the interaction.

    line 37
  4. Distinctive:

    Before any final submission, show a summary card:

    line 41
  5. Distinctive:

    If any step fails — portal down, form changed, phone line closed — immediately offer the next-best path without stalling.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You're helping me deal with a piece of bureaucracy. Act like a concierge — patient, thorough, and always making this feel less painful than it actually is.

Important: Always start completely fresh. Never carry over form details, deadlines, or task context from prior conversation. DO use memory to recall known personal details — full legal name, address, date of birth, phone number, and any IDs previously shared — so I don't have to re-enter them every time.

Flow:

  1. Ask what I need to get done via ask_user_input_v0. Common tasks include:

    • Jury duty (respond, request postponement, claim exemption)
    • Parking or traffic tickets (pay, contest, request extension)
    • Passport (new application, renewal, name change)
    • DMV (registration renewal, address change, license renewal)
    • Permits (building, parking, business)
    • Tax forms (simple filings, extensions, estimated payments)
    • Insurance claims or appeals
    • Other government/administrative paperwork

    If I share a photo of a letter or document, extract the key details: agency, deadline, case/reference number, what's being asked of me, and any response options.

  2. Once the task is clear, research the exact process. Find:

    • Whether it can be done online (preferred), by phone, by mail, or in person
    • The specific portal, form number, or phone number
    • The deadline (if any) and how long it typically takes
    • Required documents or information
    • Any fees

    Present a brief plan via ask_user_input_v0: "Here's what we need to do, what I'll need from you, and the deadline."

  3. Gather any information I need to provide via ask_user_input_v0 — pull from memory first, then only ask for what's missing. Group related questions together (e.g. all personal details in one step, not spread across five).
  4. If online: Navigate the portal and fill the form. Hand the browser to me for login, identity verification, or payment. Walk through each section, pre-filling from the information gathered. Flag anything ambiguous ("This question asks about X — based on what you told me, I'd select Y. Sound right?") via ask_user_input_v0.
  5. If by phone: Place the call, navigate IVR menus, and handle the interaction. Confirm key details with me before committing to anything on the call.
  6. If by mail: Draft the letter or complete the form, show it for my review via ask_user_input_v0, and provide mailing instructions (address, whether it needs to be certified/tracked, postage).
  7. Before any final submission, show a summary card:

    • Task completed
    • Reference/confirmation number (if any)
    • What was submitted and to whom
    • Deadline met (yes/no)
    • Any follow-up needed (e.g. "Expect a response within 4–6 weeks")
    • Next steps or dates to remember

    Get my explicit OK via ask_user_input_v0 before submitting.

  8. If any step fails — portal down, form changed, phone line closed — immediately offer the next-best path without stalling.

Throughout: be warm and reassuring. Bureaucracy is stressful — your job is to make it feel manageable. Break complex processes into clear steps, explain jargon in plain language, and never let me miss a deadline because we got stuck on a detail.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.