spk-meta-skill-authoring

Guides authoring of Spec Kitty skills using naming conventions and lifecycle families.

1.6k|156|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-meta-skill-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spk-meta-skill-authoring
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spk-meta-skill-authoring
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-meta-skill-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams extending Spec Kitty need consistent rules for naming new skills, organizing them into lifecycle families, and keeping doctrine, slash commands, and Agent Skills properly separated.

Core Features & Use Cases

  • Naming Convention Enforcement: Applies the spk-<family>-<action-or-topic> pattern for public operating skills.
  • Lifecycle Family Taxonomy: Restricts skills to established families such as start, mission, run, gate, admin, team, doctrine, integrate, and meta.
  • Boundary Rules: Keeps generated slash-command files separate from spec-kitty.<command> Agent Skills and keeps mission behavior in doctrine composition rather than skill prose.
  • Use Case: When adding a new review-gate skill to Spec Kitty, use this skill to pick the correct family, name it consistently, preserve legacy spec-kitty-* aliases, and add tests for the public skill inventory.

Quick Start

Ask the agent to author a new Spec Kitty skill for the run family following the spk naming convention and doctrine boundaries.

Frequently Asked Questions about spk-meta-skill-authoring

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

FAQPage Schema
How do I name a new Spec Kitty skill?

Name public operating skills using the pattern spk-<family>-<action-or-topic>, where the family comes from the established set: start, mission, run, gate, admin, team, doctrine, integrate, or meta. Only introduce a new family if it improves discovery.

What skill families does Spec Kitty support?

Spec Kitty defines nine established families: start, mission, run, gate, admin, team, doctrine, integrate, and meta. New skills should use one of these unless a new family clearly improves discovery.

Should slash commands and Agent Skills be kept separate in Spec Kitty?

Yes. Generated slash-command files must stay separate from generated spec-kitty.<command> Agent Skills. This boundary keeps the command surface distinct from the skill definitions loaded into agent context.

Can I keep legacy spec-kitty-* skills when adding new spk skills?

Yes. Legacy spec-kitty-* skills should be preserved when they remain useful as aliases or detailed workflows, so existing users and documentation do not break during migration to the spk naming scheme.

Where should mission behavior live in Spec Kitty?

Mission behavior belongs in doctrine mission composition, not in skill prose. Skills define operational instructions, while doctrine handles how missions are composed and executed.