agent-creator
Skill29 starsChanged 7 months agoMITView on GitHub
Authors lean, role-driven agent definitions in Markdown (responsibilities, decision framework, constraints, outputs, completion and handoff, collaboration) for use in any project or product. Use when creating `*-agent.md` files, standardizing a portable agent library, or refactoring ad-hoc prompts so they stay scannable and under a reasonable context budget.
26 other projects use a version of this.
Adopted by
Most recently taken up by
- Arcanea-Labs/Starlight-Intelligence-Systemtheir own version, first seen Nov 8, 2026
- krzysztofsurdy/code-virtuosotheir own version, first seen Nov 1, 2026
- coroboros/agent-skillstheir own version, first seen Oct 29, 2026
- 10CG/aria-plugintheir own version, first seen Oct 20, 2026
- Ronnasayd/aipptheir own version, first seen Oct 20, 2026
- AllanSantos-DV/skill-kittheir own version, first seen Oct 15, 2026
Used with
Projects with it also use security, skill-creator and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
0xSeroSkillsecurity
Also in 4 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 10 projects that use this
SentrySkillsecurity-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 5 projects that use this
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- OpenHands/extensions★ 167same name
- 9thLevelSoftware/legion★ 76same name
- DGouron/review-flow★ 42same name
- monaccode/astromesh★ 39same name
- krzysztofsurdy/code-virtuoso★ 36same name
- different-ai/openwork-hub★ 35same name
- mhylle/claude-skills-collection★ 20same name
- WalletConnect/skills★ 14same name
- Arcanea-Labs/Starlight-Intelligence-System★ 10same name
- frankxai/Starlight-Intelligence-System★ 10same name
16 more not listed
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 repository13 other files it gives its agents.
- agent-skill-creatorSkill
- art-engineSkill
- capability-architectureSkill
- copy-sanitizerSkill
- intent-replaySkill
- md-compressorSkill
- md-design-systemSkill
- opportunity-gap-finderSkill
- project-graphSkill
- skill-scanSkill
- story-architectSkill
- token-estimatorSkill
- vector-drawingSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Keep agents concise while preserving operational clarity.
- Distinctive: line 18
Add role summary only if Identity is not enough.
- Distinctive: line 19
Add responsibilities, decision framework, constraints, outputs, and collaboration.
- Very specific: line 20
Add required Failure modes and recovery micro-section.
- Very specific: line 21
Add required Completion and handoff section.
- Distinctive: line 22
Add optional sections only when they add signal.
- Distinctive: line 23
Run compression pass (dedupe, shorten, reference reusable detail).
- Distinctive: line 24
Run hard QA gate before delivery.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Creator
Summary
- Build role-driven agent files that are portable and scannable.
- Keep agents concise while preserving operational clarity.
- Require explicit completion and handoff behavior in every agent.
Core Workflow
- Name the file in kebab-case using
<role>-agent.md. - Fill Identity as one paragraph from the template.
- Add role summary only if Identity is not enough.
- Add responsibilities, decision framework, constraints, outputs, and collaboration.
- Add required
Failure modes and recoverymicro-section. - Add required
Completion and handoffsection. - Add optional sections only when they add signal.
- Run compression pass (dedupe, shorten, reference reusable detail).
- Run hard QA gate before delivery.
- Apply final formatting pass using the available MD Design System skill.
Non-Negotiable Rules
- File name — Must be
<descriptor>-agent.md. - Required sections — Responsibilities, decision framework, constraints, failure modes, outputs, collaboration, completion and handoff.
- Completion contract — Must include DoD, stop condition, next role + package, and start rule.
- Identity format — Single paragraph only.
- Readable Markdown — Minimal bold; list-first; no emphasis noise.
- Brevity target — Roughly 250-500 words per agent.
- Portability — No mandatory repo-local paths.
- Skill boundary — Agent defines role behavior; separate skills define reusable procedures.
- Final formatter — Before final output, run generated files through the local MD design system formatter.
Output Contract
- Agent file is usable as-is in system instructions.
- Reader can quickly identify boundaries, outputs, and handoff rules.
- Next role can start from the handoff package without ambiguity.
Reference Index
- Completion and handoff requirements: references/completion-and-handoff.md
- Agent template and section order: references/agent-file-template.md
- Naming and layout rules: references/naming-and-layout.md
- Authoring process and review flow: references/authoring-workflow.md
- Hard pass/fail QA gate: references/qa-rubric.md
- Failure-mode section patterns: references/failure-modes.md
- Role-family compact exemplars: references/role-family-exemplars.md
- Role vs persona distinction: references/role-vs-persona.md
- Collaboration patterns: references/collaboration-patterns.md
- Final Markdown formatting contract: available MD Design System skill
When To Use This Skill
- Creating or rewriting role-based agent files.
- Standardizing agent libraries across repos.
- Converting verbose persona prompts into operational role specs.
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.

