skill-creator

Guides creation and validation of SKILL.md-based agent skill packages.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/X-manist/Cohmira --skill skill-creator-x-manist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/X-manist/Cohmira/tree/main/boss/desktop/electron/builtin-skills/skill-creator
Command: npx skills add https://github.com/X-manist/Cohmira --skill skill-creator-x-manist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Creating a well-structured agent skill requires knowing the SKILL.md frontmatter format, naming rules, progressive disclosure patterns, and validation steps, which are easy to get wrong without a reference workflow. ## Core Features & Use Cases - Structured Skill Authoring: Walks through a six-step process from understanding use cases to initializing, editing, validating, and iterating on a skill. - Progressive Disclosure Guidance: Explains how to split content between SKILL.md, references, scripts, and assets to keep context usage lean. - UI Metadata Generation: Covers generating agents/openai.yaml interface metadata such as display name, short description, and default prompt. - Use Case: A developer wants to package a repeatable PDF-rotation workflow as a reusable skill; this skill guides naming the folder, writing the frontmatter description, adding a script, and running validation. ## Quick Start Use the skill-creator skill to scaffold and validate a new skill named pdf-rotator in my skills directory.

Frequently Asked Questions about skill-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new agent skill with SKILL.md?

Create a folder named after the skill containing a SKILL.md file with YAML frontmatter defining name and description, followed by Markdown instructions. Optionally add scripts, references, and assets directories, then run a validation script to check frontmatter and naming rules.

What should go in the SKILL.md description field?

The description should state what the skill does and include specific triggers for when to use it, since it is the primary mechanism for skill discovery. Keep all when-to-use information in the frontmatter, not the body.

When should I use scripts versus references in a skill?

Use scripts for deterministic, repeatedly rewritten code that can execute without loading into context. Use references for documentation the agent reads on demand, such as schemas, API docs, or detailed workflow guides.

What is the agents/openai.yaml file used for?

The openai.yaml file holds UI-facing metadata such as display_name, short_description, icons, brand color, and a default prompt. It is read by the host product's interface, not by the agent during skill execution.

How long should a SKILL.md body be?

Keep the SKILL.md body under 500 lines and focused on essential workflow guidance. Move detailed reference material, schemas, and examples into separate reference files linked from SKILL.md.