agentleFS
Sign inStart free
omdenkar2-uiomdenkar2-ui/all-in-one/skills/aio-agents/SKILL.md

aio-agents

Skill0 starsChanged 31 days agoMITView on GitHub

Engineer agent state, tool authority, model decisions, budgets and durable checkpoint recovery.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read agent workflows and the accepted architecture.

    line 12
  2. Distinctive:

    Use aio-tdd and aio-test to exercise invalid model output, reducers/routes, unauthorized tools, budget exhaustion, duplicate effects, old …

    line 16

≈ “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

AIO Agents

Engineer agent state, tool authority, model decisions, budgets and durable checkpoint recovery.

Protocol

  1. Read agent workflows and the accepted architecture. Define typed state, partial updates/reducers, transitions, terminal conditions and stable run/operation IDs.
  2. Separate model proposals from application authorization and execution. Derive tenant/permissions from trusted context, validate tool arguments, scope credentials and treat retrieved text/tool output as untrusted data.
  3. Budget model calls/tokens, tools, wall time, concurrency and repair attempts. Define errors, cancellation and terminal status without letting retries create unbounded work.
  4. Choose durable state and effect receipts from actual recovery needs. Keep nondeterministic/effectful calls outside replayed workflow logic and reconcile crash-after-effect ambiguity with stable idempotency identity.
  5. Use aio-tdd and aio-test to exercise invalid model output, reducers/routes, unauthorized tools, budget exhaustion, duplicate effects, old checkpoints and restart.

Return and handoff

An agent architecture/implementation with state/tool contracts, budget and recovery evidence; no arbitrary tool authority granted by a prompt.

In a pipeline, use the stage contract and return to the integrating controller. Run only this specialist's owned scope; preserve the user's accepted decisions and existing authorization.

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.

Check your setup, free