api-agent
Skill0 starsChanged 3 months agoLicence not identifiedView on GitHub
From a platform-specific Knowledge Base (KB) plus a Statement of Work / solution doc (SOW), produce an LLD/ED — a Low-Level Design / Execution Document — a structured, ordered, fully-specified, SELF-CONTAINED execution plan that a SEPARATE Runner agent later carries out. The KB's shape determines the execution surface (the skill detects it — no mode to pass): a REST API contract (endpoints, methods, schemas, status codes, auth, pagination) yields steps that are HTTP calls; a product web-flow KB (pages, navigation, UI actions, selectors, success cues) yields steps that are browser-agent actions. The skill resolves the KB + SOW into a ready-to-execute plan and writes it to the output directory (default fallback `outputs/<client>/lld/`); the Runner executes from the document ALONE and never opens the KB. This skill does NOT authenticate, hold secrets, pick the environment, or make any live call/click — it only DESIGNS the execution; the Runner executes it. Platform-agnostic: every endpoint, method, auth flow, status meaning, page, and selector comes from the KB; the SOW says WHAT workflow to run. Use when an operator points at a KB + SOW and wants the execution document a Runner will follow. Triggers: "create the LLD / execution doc from this KB + SOW", "design the {platform} API workflow", "design the browser flow from the KB", "api-agent", "produce the runbook the Runner will execute".
- Reads credentials
In this repository10 other files it gives its agents.
- apply-fixesSkill
- browser-agentSkill
- code-agentSkill
- config-agentSkill
- diagnose-bugSkill
- document-generatorSkill
- find-bugsSkill
- kb-builderSkill
- process-comparisonSkill
- runner-agentSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.