Agent skill
create-command
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.
Install this agent skill to your Project
npx add-skill https://github.com/mindfold-ai/Trellis/tree/main/packages/cli/src/templates/codex/skills/create-command
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
- 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 |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
create-command
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.
finish-work
Pre-commit quality checklist covering lint, typecheck, tests, code-spec sync, API changes, database migrations, cross-layer verification, and manual testing. Blocks commit if infra or cross-layer specs lack executable depth. Use when code is written and tested but not yet committed, before submitting changes, or as a final review before git commit.
update-spec
Captures executable contracts and coding knowledge into .trellis/spec/ documents after implementation, debugging, or design decisions. Enforces code-spec depth for infra and cross-layer changes with mandatory sections for signatures, contracts, validation matrices, and test points. Use when a feature is implemented, a bug is fixed, a design decision is made, a new pattern is discovered, or cross-layer contracts change.
check
Validates recently written code against project-specific development guidelines from .trellis/spec/. Identifies changed files via git diff, discovers applicable spec modules, runs lint and typecheck, and reports guideline violations. Use when code is written and needs quality verification, to catch context drift during long sessions, or before committing changes.
check-cross-layer
Post-implementation verification across multiple code dimensions: cross-layer data flow, code reuse analysis, import path validation, and same-layer consistency checks. Identifies missed update sites, type mismatches, and duplicated constants. Use when changes span 3+ architectural layers, after modifying shared constants or configs, after batch file modifications, or when creating new utility functions.
start
Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/. Classifies incoming tasks and routes to brainstorm, direct edit, or task workflow. Use when beginning a new coding session, resuming work, starting a new task, or re-establishing project context.
Didn't find tool you were looking for?