The Claude Skill Factory for Strategy: Build Your Own Skills
Most people solve a recurring strategic problem by writing a better prompt, then writing it again next month, slightly differently, with the same generic result. The Claude Skill Factory for Strategy is not a skill, it is the method for building one. It turns "I keep asking Claude to help me think through X and the output is never quite right" into a named, versioned, reusable skill that produces the same rigor every time you invoke it, across 8 meta-skills.
Free skills and prompts for Claude and strategy work
Templates for Claude, ChatGPT and Perplexity — from diagnostics to board-ready decks.
What the Claude Skill Factory for Strategy is
Every other skill pack on this site hands you a finished tool: a skill that already knows how to size a market, stress-test a growth plan, or structure a board narrative. The Claude Skill Factory for Strategy hands you something different, the mechanism for making that kind of tool yourself, for the specific recurring problem that only you actually have. Nobody can pre-package a skill for "the weird recurring analysis my team asks me to redo every quarter in a slightly different shape." That skill doesn't exist yet. The factory is how you build it, properly, in an afternoon, instead of limping along on a prompt you retype from memory every time.
One-off prompting fails for recurring work for a structural reason, not a skill-issue reason: a prompt is stateless and a strategic need is not. When you ask Claude to help you think through the same recurring question for the fifth time, you are re-deriving the same judgment calls, what counts as evidence, what the output should look like, what a reviewer would immediately flag as missing, from memory, under time pressure, and slightly differently each time. A skill fixes the method once, in writing, so the quality stops depending on your memory or your mood.
Most homemade custom instructions degrade into generic advice for four specific, avoidable reasons: they describe a topic instead of a procedure, they have no forced output structure so Claude reaches for whatever shape feels natural, they have no guardrails so nothing stops an invented number or a padded answer, and they drift, living in someone's head or a stale doc with no version history.
The factory closes each of those four gaps in sequence and produces an actual file, a SKILL.md, that Claude can be told to invoke by name. What comes out the other end is not a better prompt. It is a small, testable, named instrument that produces the same quality of judgment on the tenth use as it did on the first, and that you, or anyone on your team, can hand to someone else without a training session.
Download all 8 skills
One zip, one folder per skill. Free, no signup.
The 8 skills in The Claude Skill Factory for Strategy
The factory runs in the order a real skill gets built, diagnose first, deploy last, but every meta-skill is also useful on its own for a targeted task.
Stage 1 · 2 skills
Diagnose the Real Recurring Need
Most requests for a custom Claude skill start as a complaint about bad output, not a scoped brief. This stage forces the translation from Claude's answers always being generic into a precise statement of the decision the skill needs to serve, who reviews the output, and exactly how the current ad hoc approach fails.
Strategic Need Diagnosis
Use when: You have a recurring task you keep re-prompting for, and you can feel the output is off but haven't pinned down why
Output: A one-page need statement naming the recurring decision, the real audience/reviewer, and the specific failure pattern in current attempts
Failure Mode Autopsy
Use when: You have three or more past Claude outputs for this task and want to know exactly what a reviewer would strike out, rather than guessing
Output: A ranked list of concrete failure patterns tied to specific lines in the sample outputs
Stage 2 · 2 skills
Design the Skill's Mandate and Method
This is where you decide what the skill actually enforces, not what Claude should say, but what Claude must do to earn the right to say it. A skill's value comes almost entirely from the method and structure locked in here.
Skill Mandate Specification
Use when: You know the failure mode and need to convert it into a design brief before anyone writes a line of instruction text
Output: A mandate document defining the skill's single job, its non-goals, its required inputs, and the analytical method it will force
Output Blueprint Design
Use when: You have a mandate but the eventual output could still take five different shapes, and you need to lock one before writing instructions
Output: A literal section-by-section template every future run must fill exactly, with placeholder content showing what belongs in each section
Stage 3 · 1 skill
Author the SKILL.md Instruction File
This stage turns the mandate and blueprint into the actual file Claude reads. The discipline here is compression and precision: a skill that rambles is a skill Claude will selectively ignore under token pressure.
SKILL.md Drafting
Use when: You have a finished mandate and output blueprint and need to turn them into a properly formatted instruction file with a name Claude can be told to invoke directly
Output: A complete, ready-to-save SKILL.md: role statement, numbered method, exact output template, explicit guardrails, and one worked example
Stage 4 · 2 skills
Stress-Test the Draft Against a Quality Bar
A skill that only works on the tidy example you wrote it against is not a skill, it's a demo. This stage runs the draft against messy, sparse, and adversarial inputs on purpose, then checks the result against an objective bar.
Adversarial Input Testing
Use when: The SKILL.md draft exists and has only ever been tested on clean input — you need to know what it does when the input is thin, contradictory, or trying to trick it into inventing content
Output: A test log of deliberately bad inputs paired with what the skill produced and whether it correctly flagged the gap
Skill Quality Audit
Use when: The draft has passed adversarial testing and you need an objective pass/fail check against a fixed bar before anyone downstream relies on it
Output: A scored checklist verdict (pass/revise/reject) against the eight quality-bar criteria, with the specific line cited for any failing criterion
Stage 5 · 1 skill
Package, Name, and Version the Skill
A validated SKILL.md that lives in a random folder with no version number and no invocation instructions will be forgotten in a month. This stage turns a passed draft into something a whole team can find, invoke by name, and safely revise later.
Skill Packaging and Versioning
Use when: The skill has passed the quality audit and you need to finalize its folder structure, name, invocation instructions, and version number
Output: A finalized skill package (SKILL.md plus a one-line changelog entry and invocation instructions) at version 1.0, with a defined rule for when a future edit becomes a minor vs major version
Setup guide
Download the skills pack
The zip contains all 8 skills, one folder per skill, each with a single SKILL.md file. Unzip it anywhere. Keep the whole set, or pull out just the skills you need.
Create a Claude Project
Go to claude.ai, open the left sidebar, click Projects, then Create Project. Name it something like "Skill Factory" so you can reuse it every time you build a new skill.
Add the skills as Project Knowledge
Inside your project, open Project Knowledge, click Add Content, and upload the .md files. Add one stage or all 8 skills. Claude references them automatically in every conversation inside that project.
Run the stages in sequence
Open a new conversation inside the project, give Claude the recurring task you keep re-prompting for, and name the meta-skill you want it to run. Chain the output of one stage into the next in the same session.
Example prompts
- "Use the strategic-need-diagnosis skill on this: I keep asking Claude to help me think through competitor launches and it never quite lands."
- "Use the failure-mode-autopsy skill on these three past outputs and tell me exactly what a reviewer would strike out."
- "Use the skill-md-drafting skill to turn this mandate and output blueprint into a finished SKILL.md."
- "Use the skill-quality-audit skill to score this draft against the eight-point quality bar before I ship it."
Tip
Name the skill in your prompt instead of describing the task. Phrases like "use the adversarial-input-testing skill" point Claude at the exact method instead of leaving it to guess.
How to choose a skill from The Claude Skill Factory for Strategy
Match your immediate situation to the skill that answers it. For a wider set of standalone strategy skills beyond this pack, see our strategy skills for Claude Fable 5, and for the wider path from thinking to slides, see our consultant's guide to Claude.
The quality bar
Every skill built through The Claude Skill Factory for Strategy is checked against this bar before it ships, so it holds up in a partner or board review, not a generic best-practice summary.
Frequently asked questions
What is the Claude Skill Factory for Strategy, exactly?
It's a repeatable, staged method, delivered as a set of meta-skills, for designing, writing, testing, and shipping your own custom Claude skill for a recurring strategic task you have. It doesn't do strategy work itself; it produces the tool that does. Think of it as a production line for skills rather than a single skill.
How is this different from just prompting Claude directly each time?
Ad hoc prompting re-derives the method, structure, and standards from memory every time, so quality varies with how well you happened to phrase that day's request. A skill built through this factory fixes the method, output structure, and guardrails once, in writing, so the tenth use is as rigorous as the first, and anyone on your team can invoke it with the same result.
Do I need to run every stage every time?
For a first skill, yes, skipping diagnosis or validation is exactly how homemade instructions end up generic. For a minor revision to an existing, already-validated skill, you can often re-enter at the Author or Validate stage directly, as long as the mandate itself hasn't changed.
What do I actually need to use this?
A Claude account with access to Projects or a skills directory where a SKILL.md file can be saved and invoked by name, and at least one real example of the recurring task you're building the skill for, since diagnosis and testing both depend on having actual material to work against.
Can the output of a skill I build this way feed into Oria for slides?
Yes, a skill built through this factory that produces a structured strategic output, such as a verdict, a ranked analysis, or a decision memo, is a clean input for turning into a deck, since Oria works from structured content rather than freeform prose.