Use historical analogies to inform strategic decisions by identifying structural similarities and differences between past and present situations. Use this skill when the user draws on historical precedent to justify a strategy, needs to evaluate whether a historical comparison is valid, or wants to learn from past events — even if they say 'this is like the dotcom bubble', 'history repeats itself', or 'what can we learn from how X handled this'.
npx skills add https://github.com/asgard-ai-platform/skills --skill hum-historical-analogy
Historical analogies apply lessons from past events to current decisions. When used rigorously, they provide pattern recognition and foresight. When used carelessly, they mislead by overfitting superficial similarities and ignoring structural differences.
IRON LAW: Structural Similarity, Not Surface Similarity
A valid analogy requires shared STRUCTURAL features (causal mechanisms,
power dynamics, systemic patterns), not just surface resemblance.
"This startup is the next Apple" because the founder wears turtlenecks =
surface similarity (worthless). "This market has the same demand-side
network effects as early smartphone adoption" = structural similarity (useful).
| Trap | Description | Example |
|------|-----------|---------|
| Cherry-picking | Selecting only the historical case that supports your conclusion | "Kodak failed to adapt, so we must pivot" (ignoring cases where staying the course was right) |
| Outcome bias | Using the historical outcome to validate the analogy | "Amazon survived the dotcom bust, so we will too" (survivorship bias) |
| False precision | Expecting history to repeat exactly | "The 2008 crisis took 18 months to recover, so this one will too" |
| Presentism | Judging past decisions by present knowledge | "They should have seen the crisis coming" (they didn't have today's data) |
# Historical Analogy Assessment: {Current Situation} ↔ {Historical Event}
## The Analogy
"{Current situation} is like {historical event} because..."
## Structural Similarities
| Feature | Historical | Current | Similarity |
|---------|-----------|---------|-----------|
| {mechanism} | {how it worked then} | {how it works now} | Strong/Moderate/Weak |
## Structural Differences
| Feature | Historical | Current | Impact on Analogy |
|---------|-----------|---------|------------------|
| {factor} | {then} | {now} | Weakens/Neutral/Strengthens |
## Validity Assessment
- Overall analogy strength: Strong / Moderate / Weak
- Valid for: {what aspects of the decision the analogy informs}
- Invalid for: {where the analogy breaks down}
## Lessons (with caveats)
1. {lesson} — caveat: {where this might not apply}
Scenario: "AI in 2025 is like the Internet in 1995"
| Structural Similarity | Internet 1995 | AI 2025 | Strength |
|----------------------|---------------|---------|----------|
| General-purpose technology enabling many applications | ✓ | ✓ | Strong |
| Early hype cycle with inflated expectations | ✓ (dotcom) | ✓ (AI bubble concerns) | Strong |
| Infrastructure buildout phase (broadband then, GPU/data centers now) | ✓ | ✓ | Strong |
| Structural Difference | Internet 1995 | AI 2025 | Impact |
|----------------------|---------------|---------|--------|
| Deployment speed | Years for broadband rollout | AI accessible via API in minutes | Weakens (faster adoption) |
| Incumbent response | Incumbents slow to respond (Blockbuster, newspapers) | Incumbents adopting aggressively (Microsoft, Google) | Weakens (harder for startups) |
| Regulatory environment | Minimal regulation | Active AI regulation globally (EU AI Act) | Weakens (more constraints) |
Verdict: Moderate analogy — valid for understanding the hype cycle pattern and infrastructure investment phase, but invalid for predicting startup vs incumbent dynamics ✓
references/thinking-in-time.mdGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take asgard-ai-platform/hum-historical-analogy from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.