skill-creator

Creates LLM-first skill units with valid frontmatter and structured instruction sections.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill skill-creator-carloswilliamsr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/CarlosWilliamsR/SketchOS/tree/main/.config/opencode/skills/skill-creator
Command: npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill skill-creator-carloswilliamsr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams repeatedly explain the same conventions and workflows to AI agents, and ad-hoc prompts produce inconsistent results. This Skill standardizes how reusable AI instruction contracts (skills) are authored so agents activate the right guidance every time. ## Core Features & Use Cases - Skill Scaffolding: Generates SKILL.md files with required frontmatter (name, description, license, metadata) and ordered sections: Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, References. - Style Guide Enforcement: Applies the repo's docs/skill-style-guide.md or the bundled references/skill-style-guide.md copy, with inline fallback rules when neither is available. - Token Budget Control: Enforces a 180-450 token body target with a 1000-token hard maximum, moving detail into assets/ or references/. - Use Case: When your team keeps re-explaining how to format Jira tickets to an AI agent, use this Skill to create a reusable jira-task skill with trigger words, hard rules, and a decision table. ## Quick Start Create a new skill for our team's Jira ticket creation workflow following the skill style guide.

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 skill for an AI agent?

Create a `skills/{skill-name}/SKILL.md` file with frontmatter containing name, description, license, and metadata, followed by sections in this order: Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, References. Keep the body between 180 and 450 tokens.

What frontmatter fields are required in a SKILL.md file?

The frontmatter must include name, description, license, metadata.author, and metadata.version. The description must be one quoted physical line, start with trigger words, and stay under 250 characters.

When should I not create a skill?

Do not create a skill when the pattern is trivial, one-off, or better served by normal documentation. Skills are meant for repeated patterns, project-specific conventions, and complex workflows needing step-by-step agent guidance.

Where do I put long examples and schemas in a skill?

Move templates, schemas, and fixtures into an `assets/` directory and conceptual detail or edge cases into `references/` as local files. The SKILL.md body has a hard maximum of 1000 tokens, so supporting material must live outside it.

Why is my skill description failing validation?

Descriptions fail when they span multiple lines, lack quotes, omit trigger words, or exceed 250 characters. Use the format: "Trigger: {trigger words}. {What the skill does}." on a single physical line.