skill-developer

Create and update SKILL.md definitions with required frontmatter and governance rules.

1|3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/vobbilis/aigile --skill skill-developer-vobbilis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-developer
Source: https://github.com/vobbilis/aigile/tree/main/.github/skills/develop-new-skills
Command: npx skills add https://github.com/vobbilis/aigile --skill skill-developer-vobbilis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill-developer guide streamlines the creation, validation, and governance of SKILL.md based skills, ensuring consistent structure and high-quality entries across the repository.

Core Features & Use Cases

  • Defines the required frontmatter (name and description) and the mandatory SKILL.md layout for every skill.
  • Provides guidance on enforcing the 500-line rule, authoritative language, and team extensibility patterns.
  • Serves as a reference for contributors, maintainers, and auditors responsible for skill quality and governance.

Quick Start

Write a new SKILL.md under .github/skills with a valid frontmatter (name and description) and follow the structured template and governance guidance to add the skill to the catalog.

Frequently Asked Questions about skill-developer

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

FAQPage Schema
How do I create a new skill definition in a repository?

To create a skill definition, write a new SKILL.md file under the .github/skills directory with valid YAML frontmatter containing both name and description fields, then follow the structured template to complete the catalog entry.

What frontmatter is required for a SKILL.md file?

The required frontmatter for a SKILL.md file mandates both a name and a description field to ensure proper skill governance and standardize documentation across the repository.

Are there file length limits when defining skill standards?

Yes, skill definitions must enforce a 500-line rule for SKILL.md files to maintain high-quality entries and ensure consistent structure across the skill repository.

How do we enforce governance and documentation standards for skills?

Skill governance is enforced by validating the mandatory SKILL.md layout, checking frontmatter requirements, applying the 500-line rule, and standardizing overall description formats and usage guidelines.

Can I modify existing skill definitions without breaking standards?

You can modify existing skills by updating the SKILL.md file while adhering to the required frontmatter, structured template, and governance rules to maintain compliance within the directory.

What is the best way to guide a team in building skills?

The best way to guide teams in building skills is using a reference that defines the mandatory SKILL.md layout, enforces the 500-line rule, and provides patterns for team extensibility.