Use Business Adventures for "why did this fail?", "analyze this crisis", "what pattern applies?", or "what would Brooks notice?
npx skills add https://github.com/simbajigege/book2skills --skill business-adventures-analysis-brooks
Knowledge source: *Business Adventures* by John Brooks.
Architecture: Orchestrator + 6 subskills. The main SKILL.md routes the user query; subskills execute the diagnostic workflows and own their reference IDs.
business-adventures-analysis-brooks/
├── SKILL.md
├── quotes/
└── subskills/
├── m1_failure_diagnosis/
│ ├── module.md
│ └── references/case_library.md
├── m2_market_panic/
│ ├── module.md
│ └── references/case_library.md
├── m3_regulatory_risk/
│ ├── module.md
│ └── references/case_library.md
├── m4_product_innovation/
│ ├── module.md
│ └── references/case_library.md
├── m5_governance_accountability/
│ ├── module.md
│ └── references/case_library.md
└── m6_fraud_institutional_fragility/
├── module.md
└── references/case_library.md
Use this skill to apply John Brooks's *Business Adventures* as a diagnostic framework for corporate failures, market panics, product launches, governance breakdowns, regulatory risk, fraud, innovation, and financial culture.
The skill does not summarize the book or predict the future by analogy. It maps a live business situation to recurring Brooks patterns: panic, hubris, communication failure, incentive drift, regulatory lag, product-market mismatch, and institutional fragility.
Human nature is the constant; institutions are the variable. Identify the repeating human pattern first, then examine how structure, incentives, rules, timing, and information flow amplify it.
| Workflow | User question pattern | Inputs | Steps | Output | Should be subskill? |
|---|---|---|---|---|---|
| Failure diagnosis | "Why did this company, product, or strategy fail?" | Company/product, timeline, market context, decisions | Pattern map, decision chain, warning signals, preventable actions | Primary failure pattern and decision correction | Yes |
| Market panic analysis | "What is happening in this crash?" | Trigger, price moves, liquidity, media, forced sellers | Panic phase, technical amplifiers, stabilizers, uncertainty | Panic diagnosis and stabilizer map | Yes |
| Regulatory risk review | "Is this practice risky?" | Practice, disclosure, materiality, enforcement context | Materiality, public usability, tolerated-practice risk, rule-change trigger | Risk level and action | Yes |
| Product and innovation review | "Will this launch or innovation work?" | Product, customers, incumbents, distribution, research | Timing test, differentiation, incumbent blind spots, commercialization | Stop/redesign/accelerate/monitor recommendation | Yes |
| Governance accountability | "Is management handling this well?" | Board, incentives, crisis response, shareholder/stakeholder power | Formal power vs real consequences, incentives, accountability | Governance diagnosis | Yes |
| Fraud and institutional fragility | "How exposed is this system?" | Trust mechanism, counterparties, collateral, disclosure, losses | Hidden exposure, responsibility transfer, contagion path, controls | Fragility map and safeguards | Yes |
Invoke this skill when the user asks:
| User question type | Must run | Optional run |
|---|---|---|
| Broad case diagnosis or postmortem | M1 Failure Diagnosis | M3, M4, M5, or M6 depending on facts |
| Market crash, liquidity stress, speculative mania, selloff | M2 Market Panic | M6 if counterparties or technical systems are central |
| Insider information, disclosure, antitrust, tax, tolerated practice | M3 Regulatory Risk | M5 if board/executive accountability matters |
| Product launch, failed product, innovation, incumbent blindness | M4 Product and Innovation | M1 for full failure postmortem |
| Board conduct, shareholder power, executive accountability, crisis leadership | M5 Governance Accountability | M3 if legal exposure is material |
| Fraud, collateral failure, hidden exposure, systemic support, institutional trust | M6 Fraud and Institutional Fragility | M2 if panic dynamics are present |
| User asks only for historical parallel | Run the closest single module | M1 if the parallel needs a broader diagnosis |
references/case_library.md; when citing Brooks-derived claims, use the IDs from the module actually run.## Brooks Pattern Diagnosis
- Situation:
- Primary module:
- Supporting modules:
- Active human pattern:
- Closest historical parallel:
## Diagnostic Chain
- Trigger:
- Decisions:
- Incentives:
- Amplifiers:
- Warning signals:
- Missing facts:
## Risk / Opportunity
- Current risk:
- Latent risk:
- Rule-maker, stabilizer, or accountable actor:
- What would change the diagnosis:
## Recommendation
- Continue / change / stop:
- Immediate action:
- What to monitor:
- Evidence needed next:
## Sources
- REF-...
| Subskill | Path | Status |
|---|---|---|
| M1 Failure Diagnosis | subskills/m1_failure_diagnosis/ | Available |
| M2 Market Panic | subskills/m2_market_panic/ | Available |
| M3 Regulatory Risk | subskills/m3_regulatory_risk/ | Available |
| M4 Product and Innovation | subskills/m4_product_innovation/ | Available |
| M5 Governance Accountability | subskills/m5_governance_accountability/ | Available |
| M6 Fraud and Institutional Fragility | subskills/m6_fraud_institutional_fragility/ | Available |
When the user asks for sources, or when producing a formal analysis, cite the quote files for Brooks-derived principles. Each routed module has a references/case_library.md with stable IDs mapped to the quote files and anchors below.
Quote files:
quotes/market-dynamics-quotes.md — market fluctuation, panic psychology, technical breakdown, speculative cycles.quotes/corporate-strategy-quotes.md — product failure, Edsel, Xerox, innovation, corporate decline.quotes/risk-crisis-quotes.md — fraud, crisis, regulation, institutional fragility.quotes/investor-behavior-quotes.md — stockholder power, speculation, Wall Street behavior.quotes/wall-street-wisdom-quotes.md — finance culture and recurring market lessons.Anchor mapping:
market-dynamics-quotes.md: #market-will-fluctuate, #morgans-maxim, #antiperistasis-defined, #expectation-vs-event, #tape-delay-consequences, #panic-psychology, #crisis-creates-chaos, #psychological-gestures, #bellwether-stocks, #round-number-psychology, #specialist-wisdom, #crisis-unfathomable, #speculative-cycles, #sweetness-of-honeycorporate-strategy-quotes.md: #edsel-market-research, #car-personality, #edsel-name-decision, #timing-risk, #kaiser-lesson, #styling-decisions, #image-conflict, #copies-stigma, #copies-suspicion, #corner-game, #tragic-flaw, #communication-problem, #corporate-power, #meeting-authorityrisk-crisis-quotes.md: #insider-information-value, #stacked-deck, #insider-incentive, #haupt-risk, #vegetable-oil-exposure, #exchange-responsibility, #sherman-act, #conspiracy-concealment, #price-fixing-penalty, #central-bank-purpose, #federal-reserve-role, #tax-law-scope, #two-currenciesinvestor-behavior-quotes.md: #never-give-advice, #entertainment-vs-greed, #jokes-as-attraction, #walk-ins-as-indicator, #lunch-hour-selling, #who-sold-in-crash, #mutual-funds-as-stabilizer, #funds-spotted-bargains, #losing-other-peoples-money, #fear-of-fund-redemptions, #air-of-unreality, #public-individuals-role, #margin-call-spiralwall-street-wisdom-quotes.md: #market-fragility, #edsel-lesson, #salad-oil-swindle, #stockholder-decline, #xerox-complacency, #go-go-years, #de-la-vega-observationCitation format:
> "Author's exact words here."
>
> - [*Business Adventures*, cited excerpt](https://github.com/simbajigege/book2skills/blob/main/skills/business-adventures-analysis-brooks/quotes/market-dynamics-quotes.md#panic-psychology)
Use only exact quote text from the quote files. If no exact quote fits, cite the closest anchor or module reference ID and state that the reasoning is a paraphrased Brooks application.
quotes/ or a module case_library.md.Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take simbajigege/business-adventures-analysis-brooks 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.