developing-skills

Enforce XML-based structure and validation for skill metadata.

20|4|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/mikekelly/promode --skill developing-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developing-skills
Source: https://github.com/mikekelly/promode/tree/main/plugins/promode/skills/developing-skills
Command: npx skills add https://github.com/mikekelly/promode --skill developing-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework for creating, building, reviewing, auditing, updating, and improving other skills. It codifies best practices for skill governance and proactivity, ensuring essential principles are applied before executing skill-related tasks.

Core Features & Use Cases

  • Router-based pattern guidance: Supports both simple and complex skill architectures with inline essential principles, intake, and routing.
  • Progressive disclosure discipline: Keeps SKILL.md concise by delegating details to references and workflows.
  • Validation & escalation: Defines explicit validation, escalation triggers, and testing patterns to catch issues early.
  • Domain-agnostic applicability: Useful for personal skills and distributable GitHub repos that share a consistent structure.

Quick Start

Start by outlining a minimal skill with a valid YAML frontmatter, then implement a single-file <SKILL.md> or upgrade to a router-pattern structure as complexity grows. Use templates/references to keep documentation concise and scalable.

Frequently Asked Questions about developing-skills

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

FAQPage Schema
How do I structure a skill using progressive disclosure and router patterns?

To structure a skill with progressive disclosure, keep the main SKILL.md concise and delegate detailed logic to references using a router-pattern architecture for complex workflows.

What is the best way to validate skill metadata and enforce XML-based structure?

Validating skill metadata requires enforcing an XML-based structure with explicit validation triggers and standardized workflows to catch architectural issues early during development.

How does progressive disclosure keep skill architecture maintainable as complexity grows?

Progressive disclosure maintains skill architecture by delegating granular details to references and workflows, preventing the main file from bloating as complexity increases.

Can I use this skill engineering framework for both personal skills and GitHub repos?

Yes, this domain-agnostic framework supports both personal skills and distributable GitHub repos by standardizing taxonomy, metadata, and architectural validation.

When should I upgrade a single-file SKILL.md to a router-pattern structure?

You should upgrade from a single-file SKILL.md to a router-pattern structure when skill complexity grows beyond inline principles, requiring dedicated references and escalation triggers.

Why do I need escalation triggers and validation in skill development?

Escalation triggers and validation are needed in skill development to proactively catch issues early, enforce governance, and ensure essential principles are applied before executing tasks.