Best for
- "Why did this company, product, or strategy fail?"
- "Analyze this business case."
- "What historical pattern does this resemble?"
simbajigege/book2skills/skills/business-adventures-analysis-brooks/SKILL.md
Use Business Adventures for "why did this fail?", "analyze this crisis", "what pattern applies?", or "what would Brooks notice?"
Decision brief
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.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/simbajigege/book2skills --skill "skills/business-adventures-analysis-brooks"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
Review the “Workflow Inventory” section in the pinned source before continuing.
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.
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.
Invoke this skill when the user asks:
Review the “Routing Rules” section in the pinned source before continuing.
Permission review
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
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 91/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 146 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
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.Frequently asked questions
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.
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.
Static rules flagged network in the source; the page lists the matching lines and excerpts.
Alternatives
alirezarezvani/claude-skills
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
wanshuiyin/Auto-claude-code-research-in-sleep
Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.
prowler-cloud/prowler
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
brucesongs/kali-claw
Insecure Design (OWASP A06:2025) focuses on security flaws in system architecture and design phases, rather than code implementation-level bugs.