create-master-skill

---

[!] CRITICAL EXECUTION REQUIREMENTS [!]

WORKFLOW: Build FIRST, Research SECOND, Build THIRD

MANDATORY STEPS (DO NOT SKIP):

1. [OK] Create TodoWrite with ALL phases
2. [OK] Ask integration name (e.g., "airtable", "slack", "github")
3. [OK] RUN plan-build skill to create planning build
4. [OK] PHASE 1: Web Research - comprehensive API/integration research
5. [OK] PHASE 2: Architecture Design - define master skill structure
6. [OK] PHASE 3: Build - create master skill from templates
7. [OK] PHASE 4: Validate - test and document

ANTI-PATTERN (DO NOT DO THIS): [ERROR] Skip build creation [ERROR] Start building without research [ERROR] Create master skill without understanding the integration [ERROR] Copy from notion-master without adapting [ERROR] Skip validation phase

CORRECT PATTERN (DO THIS): [OK] Ask integration → Create build → Research → Design → Build → Validate

Create Master Skill

Build production-ready master skills (shared resource libraries) for any integration.

Purpose

Master skills solve the duplication problem: When 3+ skills share common content (setup, API docs, error handling), extract it into a master skill that all can reference.

Key Insight from notion-master:

• 3 Notion skills had 950 lines of duplicated content
• After extraction: 60% context reduction (950 → 370 lines)
• Single source of truth for setup, API, errors, schemas

---

Quick Start

User says: "create master skill for Airtable"

AI does:

1. Creates planning build: {ID}-airtable-master-skill
2. Runs comprehensive web research on Airtable API
3. Designs architecture based on research
4. Builds master skill from templates
5. Validates and documents

---

Workflow

Phase 0: Initiation

[*] CREATE MASTER SKILL

What integration do you want to create a master skill for?
Examples: airtable, slack, github, linear, google-sheets, stripe

Integration name: ___________