execution/backend-executor
Skill2 starsChanged 8 months agoMITView on GitHub
Internal: Backend Executor. Implements API routes, services, business logic, auth. Read spec and segment. Write evidence on completion.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- auditSkill
- calibrationSkill
- dashboardSkill
- dry-runSkill
- executeSkill
- execution/data-executorSkill
- execution/db-executorSkill
- execution/infra-executorSkill
- execution/integration-executorSkill
- execution/ml-executorSkill
- execution/observability-executorSkill
- execution/refactor-executorSkill
- execution/release-executorSkill
- execution/security-executorSkill
- executionSkill
- execution/testing-executorSkill
- execution/ui-executorSkill
- globalSkill
- initSkill
- investigateSkill
- listSkill
- localSkill
- maintainSkill
- memorySkill
- planSkill
- registerSkill
- repairSkill
- residualSkill
- resumeSkill
- startSkill
- statusSkill
- trajectorySkill
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
- Distinctive: line 12
Do not soften the task. The executor must fix the real mechanism, not the visible symptom.
- Distinctive: line 13
Do not let the executor assume backend behavior from naming alone.
- Distinctive: line 14
Do not accept "implemented" without evidence that the changed flow, edge cases, and failure path were checked.
≈ “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.
Files
dynos-work: execution/backend-executor
Spawn the backend-executor agent with the user's prompt as the instruction.
Ruthlessness Standard
- Do not soften the task. The executor must fix the real mechanism, not the visible symptom.
- Do not let the executor assume backend behavior from naming alone. It must read the actual code paths first.
- Do not accept "implemented" without evidence that the changed flow, edge cases, and failure path were checked.
What to pass
Pass the user's full prompt verbatim. Do not summarize or sanitize it. Prepend a short hard wrapper that tells the agent to read the relevant code first, solve the underlying backend failure, and only write completion evidence after verification.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.