skill-creator

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AD-Paladins/beaconator-web --skill skill-creator-ad-paladins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/AD-Paladins/beaconator-web/tree/main/.config/opencode/skills/skill-creator
Command: npx skills add https://github.com/AD-Paladins/beaconator-web --skill skill-creator-ad-paladins

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, producing inconsistent results. This Skill standardizes how new skills are authored so every SKILL.md follows a valid, discoverable, LLM-first structure. ## Core Features & Use Cases - Skill Scaffolding: Creates skills/{skill-name}/SKILL.md 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. - Use Case: When your team keeps repeating the same Jira ticket format instructions to an AI agent, use this Skill to codify that pattern into a reusable, registered skill with proper trigger words and decision tables. ## 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 YAML frontmatter containing name, description, license, and metadata, followed by sections in this order: Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, and References.

What frontmatter is 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 guidance.

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.

Where do supporting files go in a skill directory?▼

Put templates, schemas, fixtures, and generated examples in `assets/`, and conceptual detail or links to local docs in `references/`. References must point to local files, not external URLs.