skill-issue

Create, validate, and package AI coding skills with standardized SKILL.md frontmatter.

5|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/build000r/skills --skill skill-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-issue
Source: https://github.com/build000r/skills/tree/main/skill-issue
Command: npx skills add https://github.com/build000r/skills --skill skill-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill Creator solves the challenge of designing, validating, and packaging AI coding skills by providing a standardized blueprint, frontmatter structure, and bundled resource guidelines.

Core Features & Use Cases

  • Enforces a consistent SKILL.md frontmatter (name, description) and a clear body for instructions.
  • Provides templates and scaffolding to initialize new skills with optional scripts/, references/, and assets/ directories.
  • Guides maintenance and packaging workflows, including validation before generating .skill packages.

Quick Start

Run the Skill Initializer to create a new skill directory with SKILL.md and optional resources.

Frequently Asked Questions about skill-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create and package AI coding skills with standardized SKILL.md frontmatter?

To create and package AI coding skills, you use a standardized blueprint that enforces consistent SKILL.md frontmatter, scaffolds optional directories like scripts/ and assets/, and validates everything before generating the final .skill package.

What is the best way to structure a central library of AI coding skills?

The best way to structure a central library of AI coding skills is to enforce a standardized SKILL.md frontmatter containing the name and description, while organizing supporting resources into dedicated scripts/, references/, and assets/ directories.

How does frontmatter validation work before packaging a skill for distribution?

Frontmatter validation works by checking for completeness and correct naming conventions within the SKILL.md file, ensuring all required metadata is present before integrating with packaging tools to generate a distributable .skill package.

Can I include optional scripts and references when initializing a new skill?

Yes, you can include optional scripts and references. The skill initializer provides templates and scaffolding to create new skill directories complete with SKILL.md and optional scripts/, references/, and assets/ directories.

What are the limitations of manually updating skills in a central library without a validation workflow?

Without a validation workflow, manually updating skills risks frontmatter incompleteness, naming convention drift, and packaging errors, which can break integration with downstream packaging tools before final distribution.

Do I need specific packaging tools to generate a .skill package from a SKILL.md file?

Yes, you need specific packaging tools. The skill creation process integrates with packaging tools to validate the SKILL.md frontmatter and bundle the optional scripts, references, and assets into a distributable .skill package.