strategic-narrative
Skill2 starsChanged 4 months agoNo licenceView on GitHub
Craft the movement-level story (Andy Raskin's strategic narrative) — name the old-game→new-game shift, the stakes (winners and losers), the object of the new game (Promised Land), the obstacles, capabilities as "magic gifts," and evidence the story comes true. Fires on prompts like "build a strategic narrative," "what's our why-now story," "name the shift," "old game new game," "promised land," "Raskin framework," "our pitch starts with the product and falls flat," "prospects keep asking how we're different from X," "rebuild the sales deck opener," "we need a movement, not a feature list," or "what's the campaign narrative." Also the natural next step after `positioning-messaging` when the product sells to enterprise or group buyers and needs a story bigger than a category claim. Requires an existing product hub with a chosen positioning POV in `07-positioning.md` (an `Assumption`-labeled POV counts); will say so and point back to `positioning-messaging` if that's still empty.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- marcos-sponton/frameworks-as-skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- marcos-sponton/frameworks-as-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- campaign-starterSkill
- competitor-discoverySkill
- competitor-journey-captureSkill
- competitor-positioning-pricingSkill
- context-intakeSkill
- copywritingSkill
- distribution-plannerSkill
- evidence-synthesizerSkill
- messaging-houseSkill
- positioning-messagingSkill
- product-immersionSkill
- stakeholder-alignmentSkill
- value-framingSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

