agentleFS
lxyerlxyer/multi-agent-collaboration-system/.agents/skills/create-command/SKILL.md

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

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
  1. Very specific:

    Create a new Codex skill in .agents/skills/<skill-name>/SKILL.md based on user requirements.

    line 8
  2. Very specific:

    Skill name: Use kebab-case (e.g., review-pr)

    line 26
  3. Distinctive:

    Initialization: Read docs, establish context

    line 32
  4. Distinctive:

    Pre-development: Read guidelines, check dependencies

    line 33
  5. Distinctive:

    Duplicate functionality: Check if similar skill exists first

    line 89

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 guidelines

Execution 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

  1. Clear and concise: Immediately understandable
  2. Executable: AI can follow steps directly
  3. Well-scoped: Clear boundaries of what to do and not do
  4. Has output: Specifies expected output format (if needed)

[X] Avoid

  1. Too vague: e.g., "optimize code"
  2. Too complex: Single skill should not exceed 100 lines
  3. Duplicate functionality: Check if similar skill exists first

Naming Conventions

Skill TypePrefixExample
Session Startstartstart
Pre-developmentbefore-before-dev
Checkcheck-check
Recordrecord-record-session
Generategenerate-generate-api-doc
Updateupdate-update-changelog
OtherVerb-firstreview-code, sync-data

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.