agent-authoring
Skill0 starsChanged 5 months agoMITView on GitHub
Write or edit lean, bloat-free agent definitions (one responsibility, one deliverable, without repeating the global principles). Use it only when creating or modifying a studio agent.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- DAAF-Contribution-Community/daaftheir own version, first seen Nov 3, 2026
- GGGODLIN/gggodlin-cc-harnesstheir own version, first seen Oct 20, 2026
- taurgis/sfcc-dev-mcptheir own version, first seen Jan 21, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- DAAF-Contribution-Community/daaf★ 239same name
- GGGODLIN/gggodlin-cc-harness★ 73same name
- taurgis/sfcc-dev-mcp★ 27same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- docs/AGENTS.mdAGENTS.md
- adopt-groundSkill
- architecture-decisionSkill
- asset-sourcingSkill
- brand-evaluation-rubricSkill
- criticSkill
- data-integritySkill
- diagrams-gateSkill
- drift-protocolSkill
- env-reproducibleSkill
- orchestrator-bridgeSkill
- project-cleanupSkill
- qa-eyesSkill
- qa-visual-criteriaSkill
- research-methodologySkill
- security-auditSkill
- setupSkill
- smoke-testSkill
- technical-documentationSkill
- visualizerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 7
Use it only when creating or editing an agent.
≈ “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
SKILL: agent-authoring — write/edit lean agent definitions
Use it only when creating or editing an agent. Goal: clear agents, not bloated ones.
Minimal structure
id/role · objective (1 sentence) · what it reads · ONE deliverable + its gate · criteria (bullets) · rules (RC + escalation) · model (tier).
Anti-bloat checklist (reject the definition if it fails)
- A single responsibility.
- Does NOT repeat the global principles (P-01..P-11 live in STUDIO.md).
- No contradictions, and not so rigid it prevents reasoning (OVER_CONSTRAINED).
- No references to non-existent files/skills (ORPHAN).
- Examples only if they add value (anti BLOATED).
- Unambiguous objective and deliverable (anti VAGUE).
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.