skill-creator

Create, validate, and package OpenCode skill units with scripts and reference guides.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/AGIBuild/dotnet.CI.template --skill skill-creator-agibuild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/AGIBuild/dotnet.CI.template/tree/main/.cursor/skills/skill-creator
Command: npx skills add https://github.com/AGIBuild/dotnet.CI.template --skill skill-creator-agibuild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Creating a well-structured skill for OpenCode requires knowing the SKILL.md format, frontmatter rules, progressive disclosure patterns, and packaging conventions, which is easy to get wrong without guidance. ## Core Features & Use Cases - Skill Scaffolding: Run init_skill.py to generate a complete skill directory with a SKILL.md template and example scripts, references, and assets folders. - Validation and Packaging: Use quick_validate.py to check frontmatter, naming, and description rules, then package_skill.py to produce a distributable .skill file. - Design Guidance: Follow built-in principles on conciseness, degrees of freedom, and progressive disclosure, plus reference guides for workflow and output patterns. - Use Case: When you want to teach OpenCode a repeatable workflow like PDF processing or brand guidelines, use this skill to plan, scaffold, validate, and package the new skill correctly. ## Quick Start Create a new skill named pdf-rotator in the skills directory and walk me through completing its SKILL.md.

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 OpenCode?▼

Run scripts/init_skill.py with the skill name and output path to generate a template directory containing SKILL.md plus example scripts, references, and assets folders. Then edit the SKILL.md frontmatter and body, and customize or delete the example files.

What fields are required in SKILL.md frontmatter?▼

Only name and description are required in the YAML frontmatter. The name must be kebab-case and match the directory name, while the description should explain what the skill does and when to trigger it.

How do I package a skill into a .skill file?▼

Run scripts/package_skill.py with the path to your skill folder and an optional output directory. The script validates the skill first, then creates a zip archive with a .skill extension if validation passes.

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 like schemas or API guides that OpenCode reads only when needed, keeping SKILL.md lean.

Why does skill validation fail on my description?▼

Validation fails if the description exceeds 1024 characters or contains angle brackets. It also fails on unexpected frontmatter keys, non-kebab-case names, or names longer than 64 characters.