skill-creator

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

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/albersg/dotfiles --skill skill-creator-albersg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/albersg/dotfiles/tree/main/dotfiles-opencode/.opencode/skills/skill-creator
Command: npx skills add https://github.com/albersg/dotfiles --skill skill-creator-albersg

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 at the right time. ## 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 the repo's skill-style-guide.md or a bundled fallback copy, enforcing token budgets, single-line descriptions, and trigger-word placement. - Decision Gates: Provides tables for deciding when content belongs in assets/, references/, or the main skill body. - Use Case: When your team documents a recurring Jira ticket-creation pattern, use this Skill to generate a compliant skill with proper triggers, register it in AGENTS.md, and keep the body under the token budget. ## Quick Start Ask the agent to create a new skill for a repeated workflow, for example: create a skill that documents how we format Jira tasks in this repository.

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 with a SKILL.md file containing YAML frontmatter with name, description, license, and metadata fields, followed by ordered sections: Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, and References. Register project skills in AGENTS.md.

What frontmatter is 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 starting with trigger words, ideally under 160 characters and never over 250.

When should I create a skill versus normal documentation?▼

Create a skill when a pattern repeats and the AI needs runtime guidance, when project conventions differ from generic best practices, or when workflows need decision trees. Skip skills for trivial, one-off tasks better served by regular docs.

How long should a SKILL.md body be?▼

Target 180-450 tokens for the skill body, with a recommended maximum of 700 and a hard maximum of 1000 tokens. Move examples, schemas, and background material into assets/ or references/ directories.

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. References must point to local files, not external URLs.