How the skill is built, why it works this way — and where to start if you want to change it.
A single SKILL.md with 7 stateful phases and a verification layer
The entire skill lives in a single SKILL.md — no external reference files, no scripts. The intelligence is in the structure:
Immutable core principles + current algorithm data. The skill's "world view".
State machine with 7 phases + entry point routing. Determines WHERE the skill starts.
Each phase has: Goal, guiding principle, tactics, concrete output formats.
6-point check that EVERY output passes through. Plus tonality rules.
How the skill decides where to enter and how to proceed
The skill isn't linear — it's a state machine. Users can enter at any phase — the skill routes automatically based on keywords.
P1
Positioning
P2
Profile
P3
Content
P4
Engagement
P5
Community
P6
Analytics
P7
Monetization
The skill separates WHERE to enter (orchestrator) from WHAT happens there (phase definition). Like a phone menu ("Press 1 for..., 2 for...") separate from the departments behind it. Adding a new phase = new row in the entry table + the phase itself.
How each of the 7 phases is structured
Every phase follows the same blueprint — like an interface:
One sentence describing what must be achieved. Serves as compass for Claude.
A bold conviction driving all tactics. E.g. "Commenting is the fastest path to visibility."
Concrete action items, tables, lists, formulas. The operational core.
What can go wrong and how the skill should respond.
Numbered list of deliverables. What the user holds after the phase.
Copy the 5-field structure, change content, add a row to the entry table. Done. The orchestrator itself stays unchanged — it's an open dispatcher serving unlimited phases.
6 checkpoints every output passes through
Cheat sheet for modifying the skill
→ Algorithm section + Content phase (format mix) + Verification check 1
→ Entry table + Phase with 5-field structure + optionally frontmatter
→ Only within the affected phase → Tactics section
→ Change directly, but check cascade effects
→ Only change if you understand cascade effects on ALL phases
→ Sharpen verification checks (add explicit negative examples)
Invariant principles define the world view. Volatile data provides the facts. The orchestrator routes to the right place. 7 phases with identical structure produce the answers. Verification checks everything against the principles. Changes to upper layers cascade downward — so change principles cautiously, tactics boldly.
Can you modify the skill with precision?
You want to add a new Phase 8 "LinkedIn for Recruiters". What must you change?
LinkedIn changes the algorithm: carousels now perform 50% worse, native polls are the new top format.