copy and paste what's below here
==================================================
here's the structure for creating a claude skill. follow these rules and guidelines to a t.

 
Claude Skills: Power User Guide
What a Skill Actually Is
A skill is a folder with a SKILL.md at its root, plus optional bundled resources. Claude reads the SKILL.md when triggered and follows its instructions like a mini system prompt for that task. There are no variables, loops, or iterators in the traditional programming sense — the "logic" is natural language instructions telling Claude what to do conditionally, sequentially, or branching.
The Core Structure
my-skill/
├── SKILL.md          ← required; triggers + instructions
└── references/       ← optional deep docs loaded on demand
└── assets/           ← optional templates, fonts, brand files
└── scripts/          ← optional executable code Claude can run
SKILL.md anatomy:
markdown---
name: my-skill
description: [TRIGGER TEXT — this is what Claude pattern-matches against]
---
# Instructions
...the actual directions...
The Real "Variables" — The Description Field
The description in the YAML frontmatter is the most important thing you'll write. Claude decides whether to load the skill based on this field alone. It's not code, but it functions like a matching rule.
Weak description: "Helps with marketing copy"
Strong description: "Write brand-aligned marketing copy, campaign briefs, launch announcements, ad copy, email sequences, or any customer-facing content. Use this skill whenever the user mentions campaigns, positioning, messaging, copy, launches, or asks to write anything that will be seen externally."
Key tactics:
Be pushy — skills undertrigger more than overtrigger
Include synonyms and phrasings users actually type
Mention roles ("when a marketer asks..." or "for finance team...")
Include both the what and when
"Control Flow" in Natural Language
Since there's no code interpreter in SKILL.md, you use structured prose as logic:
Branching (if/else):
markdown## Step 1: Identify Document Type
- If the user says "memo" → load `references/memo-format.md`
- If the user says "board update" → load `references/board-format.md`
- If unclear → ask: "Is this internal or external?"
Sequential (loops via numbered steps):
markdown1. Draft the section
2. Review against brand guidelines in `references/brand.md`
3. Revise if any guideline is violated
4. Repeat steps 1-3 for each section
Conditionals:
markdownIf the output is longer than 1 page, add an executive summary at the top.
```
This is the mental model: **you're writing directions for a very capable intern, not a compiler.**
---
### Progressive Disclosure — The 3-Level System
This is the key architectural concept:
| Level | What | Size | When loaded |
|-------|------|------|-------------|
| 1 | `name` + `description` | ~100 words | Always (every message) |
| 2 | SKILL.md body | <500 lines ideal | When skill triggers |
| 3 | `references/` files | Unlimited | Only when SKILL.md says to |
**Practical implication:** Keep SKILL.md as a *router*, not an encyclopedia. Put deep content in reference files and tell Claude when to read them.
---
### Reference Files — How Many / How Long?
- **SKILL.md body:** Under 500 lines. If you're going over, add a `references/` folder.
- **Individual reference files:** 300+ lines → include a table of contents at the top so Claude can navigate efficiently.
- **Number of files:** No hard limit, but organize by use case so Claude reads only what's relevant (e.g., `references/aws.md`, `references/gcp.md` — Claude reads only the one that matches the user's context).
- **Assets (images, fonts, templates):** No size limit — Claude can use these without loading them into context.
---
### Startup Role Templates to Build
Here's how this maps across your team:
**Product**
```
references/
  prd-template.md
  user-story-format.md
  feature-spec.md
```
Trigger on: "write a PRD", "spec this feature", "user stories for..."
**Marketing**
```
references/
  brand-voice.md
  campaign-brief-template.md
  email-sequences.md
  launch-checklist.md
```
Trigger on: "campaign", "copy", "launch", "email sequence", "positioning"
**Finance**
```
references/
  financial-model-conventions.md
  board-update-format.md
  budget-narrative-template.md
```
Trigger on: "board deck", "budget", "financial summary", "runway analysis"
**Ops/Recruiting**
```
references/
  job-description-template.md
  offer-letter-format.md
  process-doc-template.md
Power User Patterns
1. Chain skills via references
SKILL.md says: "First read references/brand.md, then read references/channel-specific.md based on the platform."
2. Scripts for deterministic work
Put Python/bash in scripts/ for things like file transforms, data formatting, or API calls. Claude runs them without loading them into context (efficient).
3. Asset injection
Put a Word/PPTX template in assets/ — the skill tells Claude to populate that template rather than build from scratch. Huge quality boost.
4. Persona + constraints in SKILL.md
markdown## Tone
Write like a senior operator, not a consultant. 
Avoid jargon. Max 3 bullet points per section.
Never use the word "leverage."
5. Eval loop for iteration
Write 5–10 test prompts, run them, review outputs. The skill-creator skill has a full eval harness if you want to go deep.
Quickstart for a Non-Eng Skill
Create my-skill/SKILL.md with a punchy description + 20–50 lines of instructions
Add 1–2 references/ files with templates or style guides
Test by typing a prompt that should trigger it and see if Claude reads the skill
If it doesn't trigger — rewrite the description to be more specific and "pushy"


i want you to create a skill for (super verbose explanation of a particular job to be done. consider not only the artifacts to be directly generated, but also any related artifacts to prove quality or success)
if you think you can also generate meaningful reference files, do so.