create-command
Skill1 starsChanged 7 months agoMITView on GitHub
Scaffolds a new skill file with proper naming conventions and structure. Analyzes requirements to determine skill type and generates appropriate content. Use when adding a new developer workflow skill, creating a custom skill, or extending the Trellis skill set.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- fxmartin/claude-code-configtheir own version, first seen Oct 31, 2026
- tony-hoang-ai-automation/mkt-skillstheir own version, first seen Oct 25, 2026
- pahlevikun/levistacktheir own version, first seen Oct 25, 2026
- EvolutionAPI/evo-nexustheir own version, first seen Oct 8, 2026
- KhaledSaeed18/dotclaudetheir own version, first seen Jul 4, 2026
- evolution-foundation/evo-nexustheir own version, first seen Apr 20, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- EvolutionAPI/evo-nexus★ 545same name
- evolution-foundation/evo-nexus★ 535same name
- timominkus/obsidian-para-gtd-ai★ 9same name
- KhaledSaeed18/dotclaude★ 5same name
- tony-hoang-ai-automation/mkt-skills★ 4same name
- fxmartin/claude-code-config★ 2same name
- pahlevikun/levistack★ 0same 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/macs-protocol.mdcCursor rule
- before-devSkill
- brainstormSkill
- break-loopSkill
- check-cross-layerSkill
- checkSkill
- finish-workSkill
- improve-utSkill
- integrate-skillSkill
- onboardSkill
- record-sessionSkill
- startSkill
- update-specSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
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
- Very specific: line 8
Create a new Codex skill in .agents/skills/<skill-name>/SKILL.md based on user requirements.
- Very specific: line 26
Skill name: Use kebab-case (e.g., review-pr)
- Distinctive: line 32
Initialization: Read docs, establish context
- Distinctive: line 33
Pre-development: Read guidelines, check dependencies
- Distinctive: line 89
Duplicate functionality: Check if similar skill exists first
“Common” is measured: kept by at least 6 in 10 of the 7 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
Create New Skill
Create a new Codex skill in .agents/skills/<skill-name>/SKILL.md based on user requirements.
Usage
$create-command <skill-name> <description>Example:
$create-command review-pr Check PR code changes against project guidelinesExecution Steps
1. Parse Input
Extract from user input:
- Skill name: Use kebab-case (e.g.,
review-pr) - Description: What the skill should accomplish
2. Analyze Requirements
Determine skill type based on description:
- Initialization: Read docs, establish context
- Pre-development: Read guidelines, check dependencies
- Code check: Validate code quality and guideline compliance
- Recording: Record progress, questions, structure changes
- Generation: Generate docs or code templates
3. Generate Skill Content
Minimum SKILL.md structure:
---
name: <skill-name>
description: "<description>"
---
# <Skill Title>
<Instructions for when and how to use this skill>4. Create Files
Create:
.agents/skills/<skill-name>/SKILL.md
5. Confirm Creation
Output result:
[OK] Created Skill: <skill-name>
File path:
- .agents/skills/<skill-name>/SKILL.md
Usage:
- Trigger directly with $<skill-name>
- Or open /skills and select it
Description:
<description>Skill Content Guidelines
[OK] Good skill content
- Clear and concise: Immediately understandable
- Executable: AI can follow steps directly
- Well-scoped: Clear boundaries of what to do and not do
- Has output: Specifies expected output format (if needed)
[X] Avoid
- Too vague: e.g., "optimize code"
- Too complex: Single skill should not exceed 100 lines
- Duplicate functionality: Check if similar skill exists first
Naming Conventions
| Skill Type | Prefix | Example |
| Session Start | start | start |
| Pre-development | before- | before-dev |
| Check | check- | check |
| Record | record- | record-session |
| Generate | generate- | generate-api-doc |
| Update | update- | update-changelog |
| Other | Verb-first | review-code, sync-data |
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.

