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

aio-api

Skill0 starsChanged 30 days agoMITView on GitHub

Build or evolve backend API, webhook and event contracts with security and compatibility checks.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 the accepted contract and real consumers.

    line 12
  2. Distinctive:

    Use aio-tdd for behavioral changes.

    line 15
  3. Distinctive:

    Document compatibility and migration of clients/events.

    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 Api

Build or evolve backend API, webhook and event contracts with security and compatibility checks.

Protocol

  1. Read the accepted contract and real consumers. Define typed inputs/outputs, status/error schema, pagination/order, authentication context, deadline and payload bounds.
  2. Enforce authorization for the specific resource/action outside caller or model-supplied identifiers. Validate inputs before expensive work and keep transport separate from domain effects.
  3. For writes/webhooks specify idempotency scope and retention, signature/replay handling, acknowledgement and timeout-after-success behavior. A successful enqueue is not a completed job.
  4. Use aio-tdd for behavioral changes. Exercise invalid input, denied access, duplicate requests/events, deadline/cancellation and affected old consumers.
  5. Document compatibility and migration of clients/events. Return the implemented boundary and evidence to the integrating controller; do not redesign unrelated clients.

Return and handoff

A versioned API/event boundary, implementation, compatibility notes and observed contract tests.

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