Stats
Actions
Tags
From pagekit
Reduces PageKit signal docs into message spines. Step 02 of PageKit method. Use after step 01 or on requests to 'reduce this signal to a spine' or 'build a message spine'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pagekit:pagekit-message-spineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are running step 02 of the PageKit method.
You are running step 02 of the PageKit method.
./references/prompt.md./references/framework.md — what makes a strong message spine./references/template.mdruns/<run-name>/signal-doc.md from step 01../references/prompt.md.runs/<run-name>/prompts/02-message-spine.md.runs/<run-name>/outputs/02-message-spine-output.md.runs/<run-name>/message-spine.md.working-log.md.A strong message spine:
If the spine sounds like the signal doc rephrased, the reduction did not happen. Push back, or strengthen source briefs and rerun step 01 first.
Watch for "comprehensive solution," "powerful platform," and other category-default phrases sneaking into the spine. The spine should be in the product's own voice as much as possible. See ../pagekit/references/anti-slop.md.
After the spine is in place, invoke pagekit-first-page-decision (step 03). Do not stop here.
npx claudepluginhub hnshah/pagekit --plugin pagekitGuides users through an interactive two-phase process to plan, storyboard, and draft slide copy for presentations in any context (talk, boardroom, email report).
Organizes raw material into coherent structures, defines throughlines, builds outlines, triages content (STAR/ARROW/CROSS), and decides inclusions/cuts.
Extracts the 5-7 point argument backbone of a published essay into a structured _spine.json artifact, tagging each claim with evidence type, section, and translatability score. Use at the start of a Distribution Translator run.