From strategic-analyst
Use when placing an event in historical context — precedent, analogies, cycles, path dependencies, or claims that something is "unprecedented". Triggers include "has this happened before", "is this like X", "what's the precedent", long-run trend reasoning, or structural-break vs continuation calls.
How this skill is triggered — by the user, by Claude, or both
Slash command
/strategic-analyst:analysing-historical-lensThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
History is the analyst's most abused source. Done well, it provides base rates, mechanism examples, and warning signs. Done badly, it produces lazy analogies that flatter the assumption already held. The discipline of historical analysis is *handling analogies as instruments to be calibrated, not arguments to be deployed.*
History is the analyst's most abused source. Done well, it provides base rates, mechanism examples, and warning signs. Done badly, it produces lazy analogies that flatter the assumption already held. The discipline of historical analysis is handling analogies as instruments to be calibrated, not arguments to be deployed.
Core principle: The question is never "is this like X?" — it is "in what specific respects is this like X, in what respects is it not, and what does the disanalogy imply?" (May & Neustadt, Thinking in Time).
Whenever an analogy is offered, do this explicitly:
If after this exercise the analogy still holds for the relevant mechanism, use it. If not, drop it. Munich, Vietnam, 1914, the 1930s are the most-abused analogies in policy discourse — almost always invoked to short-circuit argument.
Three time scales operate simultaneously and answer different questions:
A "shocking" event at the événementielle scale may be perfectly continuous at the conjoncturelle scale. Always check which scale the question lives at.
| Move | What to do |
|---|---|
| Someone invokes Munich/Vietnam/1914 | Run the Likeness/Difference/Presumption check |
| "This is unprecedented" | Almost never true — find the closest precedent and what it teaches |
| "This is just like the [previous decade]" | Run the same check; mind the structural differences (tech, demography) |
| Long-run trend claim ("decline of X") | Pick the right time scale; show data over the relevant period |
| "X has always Y" | Civilisational essentialism — almost always wrong; states change |
| Mistake | Fix |
|---|---|
| One-shot analogies (Munich = appeasement of all autocrats) | Specify mechanism; check structural fit |
| Hindsight bias | What did decision-makers actually know at the time? |
| Whig history / teleology | Outcomes were not predetermined; emphasise contingency at junctures |
| Survivor bias in great-power studies | Failed/absorbed states are also data |
| Cyclicality fetishism | Pattern-finding in noise; few "cycles" survive out-of-sample testing |
| "Lessons of history" applied without context | Lessons are conditional on the structure that produced them |
| Confusing precedent with cause | A pattern is not a mechanism |
| Treating short windows as long-run trends | Pull the longer series before concluding |
Headline: "China's slowdown signals end of its rise — like Japan in 1990" — through the lens:
For long-run quantitative data: Maddison Project (historical GDP), Reinhart & Rogoff data, V-Dem (long-run regime data), Correlates of War, Cross-National Time-Series Archive (1815–), national archives, Wilson Center Digital Archive (declassified diplomatic records), FRUS. See data-sources.md in the parent skill.
npx claudepluginhub alexander-newton/anacatalyst --plugin strategic-analystProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.