Source profileQuality 91/100

simbajigege/book2skills/skills/business-adventures-analysis-brooks/SKILL.md

business-adventures-analysis-brooks

Use Business Adventures for "why did this fail?", "analyze this crisis", "what pattern applies?", or "what would Brooks notice?"

Source repository stars
146
Declared platforms
0
Static risk flags
1
Last source update
2026-08-20
Source checked
2026-08-25

Decision brief

What it does: where it fits

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.

Best for

  • "Why did this company, product, or strategy fail?"
  • "Analyze this business case."
  • "What historical pattern does this resemble?"

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/simbajigege/book2skills --skill "skills/business-adventures-analysis-brooks"
Safe inspection promptEditorial

Inspect the Agent Skill "business-adventures-analysis-brooks" from https://github.com/simbajigege/book2skills/blob/f90fa7a78e4c78c92312d06fd70f7d24282c937f/skills/business-adventures-analysis-brooks/SKILL.md at commit f90fa7a78e4c78c92312d06fd70f7d24282c937f. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow Inventory

    Review the “Workflow Inventory” section in the pinned source before continuing.

    Review and apply the “Workflow Inventory” source section.
  2. 02

    Skill Purpose

    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.

    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 cultu…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-mark…
  3. 03

    Core Principle

    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.

    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.
  4. 04

    When to Use This Skill

    Invoke this skill when the user asks:

    "Why did this company, product, or strategy fail?""Analyze this business case.""What historical pattern does this resemble?"
  5. 05

    Routing Rules

    Review the “Routing Rules” section in the pinned source before continuing.

    Review and apply the “Routing Rules” source section.

Permission review

Static risk signals and limitations

Network access

medium · line 155

The documentation includes network, browsing, or remote request actions.

- [*Business Adventures*, cited excerpt](https://github.com/simbajigege/book2skills/blob/main/skills/business-adventures-analysis-brooks/quotes/market-dynamics-quotes.md#panic-psychology)

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score91/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars146SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
simbajigege/book2skills
Skill path
skills/business-adventures-analysis-brooks/SKILL.md
Commit
f90fa7a78e4c78c92312d06fd70f7d24282c937f
License
MIT
Collected
2026-08-25
Default branch
main
View the original SKILL.md

Business Adventures Analysis — Skill (John 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

Skill Purpose

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.

Core Principle

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 Inventory

WorkflowUser question patternInputsStepsOutputShould be subskill?
Failure diagnosis"Why did this company, product, or strategy fail?"Company/product, timeline, market context, decisionsPattern map, decision chain, warning signals, preventable actionsPrimary failure pattern and decision correctionYes
Market panic analysis"What is happening in this crash?"Trigger, price moves, liquidity, media, forced sellersPanic phase, technical amplifiers, stabilizers, uncertaintyPanic diagnosis and stabilizer mapYes
Regulatory risk review"Is this practice risky?"Practice, disclosure, materiality, enforcement contextMateriality, public usability, tolerated-practice risk, rule-change triggerRisk level and actionYes
Product and innovation review"Will this launch or innovation work?"Product, customers, incumbents, distribution, researchTiming test, differentiation, incumbent blind spots, commercializationStop/redesign/accelerate/monitor recommendationYes
Governance accountability"Is management handling this well?"Board, incentives, crisis response, shareholder/stakeholder powerFormal power vs real consequences, incentives, accountabilityGovernance diagnosisYes
Fraud and institutional fragility"How exposed is this system?"Trust mechanism, counterparties, collateral, disclosure, lossesHidden exposure, responsibility transfer, contagion path, controlsFragility map and safeguardsYes

When to Use This Skill

Invoke this skill when the user asks:

  • "Why did this company, product, or strategy fail?"
  • "Analyze this business case."
  • "What historical pattern does this resemble?"
  • "What would John Brooks say about this crisis?"
  • "Is this governance, compliance, or regulatory behavior a warning sign?"
  • "How do market panics typically unfold?"
  • "What lessons from Edsel, Xerox, Texas Gulf Sulphur, Piggly Wiggly, or the 1962 crash apply here?"

Routing Rules

User question typeMust runOptional run
Broad case diagnosis or postmortemM1 Failure DiagnosisM3, M4, M5, or M6 depending on facts
Market crash, liquidity stress, speculative mania, selloffM2 Market PanicM6 if counterparties or technical systems are central
Insider information, disclosure, antitrust, tax, tolerated practiceM3 Regulatory RiskM5 if board/executive accountability matters
Product launch, failed product, innovation, incumbent blindnessM4 Product and InnovationM1 for full failure postmortem
Board conduct, shareholder power, executive accountability, crisis leadershipM5 Governance AccountabilityM3 if legal exposure is material
Fraud, collateral failure, hidden exposure, systemic support, institutional trustM6 Fraud and Institutional FragilityM2 if panic dynamics are present
User asks only for historical parallelRun the closest single moduleM1 if the parallel needs a broader diagnosis

Execution Rules

  1. Read only the modules required by the routing table.
  2. If the user gives a broad failure question, run M1 first and then route to the most relevant specialist module.
  3. If the user data is thin, ask for the missing timeline, actors, incentives, disclosures, and consequences before giving a confident diagnosis.
  4. Do not run every module for a narrow question.
  5. Use historical parallels as diagnostic lenses, not as predictions.
  6. Each module owns its reference IDs in references/case_library.md; when citing Brooks-derived claims, use the IDs from the module actually run.

Multi-Module Output Format

## 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 Status

SubskillPathStatus
M1 Failure Diagnosissubskills/m1_failure_diagnosis/Available
M2 Market Panicsubskills/m2_market_panic/Available
M3 Regulatory Risksubskills/m3_regulatory_risk/Available
M4 Product and Innovationsubskills/m4_product_innovation/Available
M5 Governance Accountabilitysubskills/m5_governance_accountability/Available
M6 Fraud and Institutional Fragilitysubskills/m6_fraud_institutional_fragility/Available

CITATION RULES

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-honey
  • corporate-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-authority
  • risk-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-currencies
  • investor-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-spiral
  • wall-street-wisdom-quotes.md: #market-fragility, #edsel-lesson, #salad-oil-swindle, #stockholder-decline, #xerox-complacency, #go-go-years, #de-la-vega-observation

Citation 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.

Do Not

  • Do not treat historical parallels as deterministic forecasts.
  • Do not explain a failure only with personality when incentives or structure made the behavior rational.
  • Do not assume preparation, research, or capital equals product-market fit.
  • Do not treat tolerated practices as safe when materiality, visibility, or public pressure can change enforcement.
  • Do not confuse governance process with accountability.
  • Do not cite quote text unless it appears in quotes/ or a module case_library.md.

Frequently asked questions

What to verify before installation and use

What does the business-adventures-analysis-brooks source document cover?

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.

How do I install business-adventures-analysis-brooks?

The source record exposes this install command: npx skills add https://github.com/simbajigege/book2skills --skill "skills/business-adventures-analysis-brooks". Inspect the command and pinned source before running it.

Which permission-related actions were detected?

Static rules flagged network in the source; the page lists the matching lines and excerpts.

Alternatives

Compare before choosing

Computed 10024,921

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

Computed 10015,122

wanshuiyin/Auto-claude-code-research-in-sleep

citation-audit

Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.

Computed 10014,671

prowler-cloud/prowler

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance

Computed 9965

brucesongs/kali-claw

insecure-design

Insecure Design (OWASP A06:2025) focuses on security flaws in system architecture and design phases, rather than code implementation-level bugs.