Skill Build Kit — Golden Examples

Reference: Client Intelligence Brief

Both golden examples live in content/business/marketing/campaigns/practice-command-center/. Study these before building any new skill.

Asset Map

Skill File Structure (from Golden Example)

---
name: [skill-name]
description: >
  [Multi-line description — what it does, what input it takes,
  what output it produces, when to use it.
  Triggers: "trigger 1", "trigger 2", "trigger 3", or any request
  to [description of the job].]
metadata:
  author: Kathryn Brown, Advisory OS
  version: "[X.0.0]"
  updated: "[YYYY-MM-DD]"
---

# [Skill Name]

[One-line positioning — what the skill gives you.]

## Core Principle

**[Rule name.]** [What it means in practice — 2-3 sentences.]

## What This Skill Does

[Intro paragraph — what user pastes, what they get back.]

**Job 1: [Name]** — [What this job does. Not theory — practical output.]

**Job 2: [Name]** — [What this job does.]

**Job 3: [Name]** — [What this job does.]

## The [Output Name]: Section by Section

### 1. [Section Name]
[What this section contains, why it matters, format rules.]

### 2. [Section Name]
[...]

## Rules
- **[Rule]** [Explanation.]
- **[Rule]** [Explanation.]

## Output Format
[Complete template — exact structure with placeholders.]

## What Makes This Different
[2-3 paragraphs — why this isn't a generic prompt. Specific value proposition.]

Key Patterns from the Golden Example

YAML frontmatter: The description field is multi-line (>), includes what the skill does AND when to use it. Triggers are embedded in the description, not a separate field.

Core principle: Named and bolded. Not a vague philosophy — a specific operating rule. The CIB uses "Read before writing" — absorb all input before producing output.

Section-by-section spec: Each output section gets its own H3 with: what it contains, why it matters, format rules. Format rules are specific ("Two-column table. Numbers, Pattern, Completing, Deferring, Read — one row each. No paragraphs."). The CIB golden example has 10 sections with ~150 lines of spec — this is the longest part of the skill file. Don't shortchange it.

Rules: Stated as imperatives with bold labels. Each rule has a practical explanation. Cover: output format, scope (one client per run), quality (don't assume), edge cases (not enough data), naming conventions.

Output format: A complete markdown template with placeholders. Someone could copy this template and fill in the blanks. Every section header, every table structure, every label is shown. Use --- dividers between major sections in the template for visual separation.

"What Makes This Different": Speaks to the user, not to Claude. Contrasts with the generic alternative. Uses specific language ("catches the rolling items nobody notices") not feature-speak.

Quick-Start Structure (from Golden Example)

# [Skill Name] — Quick Start

You just got a free Claude skill. Here's how to use it.

## What You Need
- A Claude Pro account (or higher) — Skills require a paid plan
- [Input description]

## Setup (One Time)

### Step 1: Enable Code Execution
[Numbered instructions with exact UI paths]

### Step 2: Upload the Skill
[Numbered instructions — exact button names, exact sequence]

## Running the Skill
[Numbered steps — new conversation, trigger phrase, paste input, wait]

## Tips
[3-5 tips from real testing — what makes the output better]

## What to Paste
[List of accepted input types]

---
*Built by Kathryn Brown — Advisory OS*

Key Patterns from the Quick-Start

Opening line: "You just got a free Claude skill. Here's how to use it." — no welcome message, no setup.

Prerequisites: Listed as bullet points, not a paragraph. Include account requirement and input description.

Setup steps: Exact UI paths. "Click your name in the bottom-left corner" not "Navigate to settings." Each instruction is a numbered step under its own H3.

Tips: From real testing, not generic advice. "More emails = better brief" not "Include as much context as possible."

What to Paste: Simple list of accepted input types. No explanation of why — just what works.

Footer: Built by Kathryn Brown — Advisory OS — single line, italic.