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.
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Create a new Codex skill in .agents/skills/<skill-name>/SKILL.md based on user requirements.
$create-command <skill-name> <description>Example:
$create-command review-pr Check PR code changes against project guidelinesExtract from user input:
review-pr)Determine skill type based on description:
Minimum SKILL.md structure:
---
name: <skill-name>
description: "<description>"
---
# <Skill Title>
<Instructions for when and how to use this skill>Create:
.agents/skills/<skill-name>/SKILL.mdOutput 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 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 |
202780181/lingxiData
83191c9
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.