skill-creator

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

Updated May 24, 2026
One-click install
npx skills add https://github.com/etrigan16/v0-cipher-ar --skill skill-creator-etrigan16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/etrigan16/v0-cipher-ar/tree/main/.opencode/skills/skill-creator
Command: npx skills add https://github.com/etrigan16/v0-cipher-ar --skill skill-creator-etrigan16

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 instructions are authored so agents activate the right guidance with valid, discoverable frontmatter. ## Core Features & Use Cases - Skill Authoring Workflow: Guides creation of SKILL.md files with required frontmatter (name, description, license, metadata) and ordered sections from Activation Contract to References. - Style Guide Enforcement: Applies a normative LLM-first style guide with token budgets, single-line description rules, and trigger-word placement. - Decision Gates: Provides tables for deciding when content belongs in the skill body versus assets/ or references/ directories. - Use Case: When your team notices agents repeatedly mishandling a project-specific workflow, use this Skill to scaffold a new skill with correct frontmatter, concise instructions, and registration in AGENTS.md. ## Quick Start Ask the agent to create a new skill for a repeated workflow, for example: create a skill for our team's Jira ticket creation format.

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 directory containing a SKILL.md file with YAML frontmatter defining name, description, license, and metadata, followed by sections for activation contract, hard rules, decision gates, execution steps, output contract, and references. Keep the body between 180 and 1000 tokens.

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

The frontmatter must include name, description, license, and metadata with author and version. The description must be a single quoted line under 250 characters with trigger words placed first.

When should I create a skill versus writing normal documentation?▼

Create a skill when a pattern repeats, project conventions differ from generic best practices, or complex workflows need step-by-step agent guidance. Skip skills for trivial, one-off tasks better served by regular documentation.

What goes in the assets and references directories of a skill?▼

Use assets/ for code templates, schemas, fixtures, and generated examples. Use references/ for local documentation explaining concepts and edge cases. Keep the main SKILL.md body concise and move long explanations into these supporting files.

Why is my skill description not triggering agent activation?▼

Descriptions must lead with essential trigger words users or agents actually say, formatted as a single quoted YAML line. Avoid multi-line descriptions and separate Keywords sections, since discovery relies only on the frontmatter description.