create-skill

Create a directory under ~/.omp/agent/skills/<name>/ containing a SKILL.md file with YAML frontmatter defining name and description, followed by a markdown body with the procedure. Invoke it later with /skill:<name> or let the agent trigger it from the description.

Lead with what the skill does using the form 'Use when <situation>', and name concrete symptoms like error messages or failure modes. Keep it to one or two sentences, since the description is the only signal the model sees at session start.

User-scope skills live in ~/.omp/agent/skills/ and apply across all sessions, while project-scope skills live in <repo>/.omp/skills/ and only load for that repository. Default to user scope unless the skill depends on project-specific files or layout.

The frontmatter description is likely too vague or describes the action instead of the triggering situation. Tighten the symptom language, verify the file exists on disk, and confirm omp lists the skill via the skills API or a fresh session.

Yes, skills can ship optional scripts/, references/, and assets/ directories next to SKILL.md. These files are never auto-loaded into context; the SKILL.md body references them by relative path and the agent reads or runs them on demand.