Cross-functional organizational health check combining signals from all C-suite roles. Scores 8 dimensions on a traffic-light scale with drill-down recommendations. Use when assessing overall company health, preparing for board reviews, identifying at-risk functions, or when user mentions org health, health check, or health dashboard.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Eight dimensions. Traffic lights. Real benchmarks. Surfaces the problems you don't know you have.
org health, organizational health, health diagnostic, health dashboard, health check, company health, functional health, team health, startup health, health scorecard, health assessment, risk dashboard
python scripts/health_scorer.py # Guided CLI — enter metrics, get scored dashboard
python scripts/health_scorer.py --json # Output raw JSON for integration
Or describe your metrics in natural language:
"Run an org health check" — paste your key metrics or answer prompts "Score our [financial|revenue|product|engineering|people|ops|security|market] health" — single-dimension deep dive
What it measures: Can we fund operations and invest in growth?
Key metrics:
What it measures: Are customers staying, growing, and recommending us?
Key metrics:
What it measures: Do customers love and use the product?
Key metrics:
What it measures: Can we ship reliably and sustain velocity?
Key metrics:
What it measures: Is the team stable, engaged, and growing?
Key metrics:
What it measures: Are we executing our strategy with discipline?
Key metrics:
What it measures: Are we protecting customers and maintaining compliance?
Key metrics:
What it measures: Are we winning in the market and growing efficiently?
Key metrics:
Each dimension is scored 1-10 with traffic light:
Overall Health Score:
Weighted average by company stage (see references/health-benchmarks.md for weights).
| If this dimension is red... | Watch these dimensions next |
|---|---|
| Financial Health | People (freeze hiring) → Engineering (freeze infra) → Product (cut scope) |
| Revenue Health | Financial (cash gap) → People (attrition risk) → Market (lose positioning) |
| People Health | Engineering (velocity drops) → Product (quality drops) → Revenue (churn rises) |
| Engineering Health | Product (features slip) → Revenue (deals stall on product) |
| Product Health | Revenue (NRR drops, churn rises) → Market (CAC rises; referrals dry up) |
| Operational Health | All dimensions degrade over time (execution failure cascades everywhere) |
ORG HEALTH DIAGNOSTIC — [Company] — [Date]
Stage: [Seed/A/B/C] Overall: [Score]/10 Trend: [↑ Improving / → Stable / ↓ Declining]
DIMENSION SCORES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
💰 Financial 🟢 8.2 Runway 14mo, burn 1.6x — strong
📈 Revenue 🟡 5.8 NRR 104%, pipeline thin (1.8x coverage)
🚀 Product 🟢 7.4 NPS 42, DAU/MAU 38%
⚙️ Engineering 🟡 5.2 Debt at 30%, MTTR 3.2h
👥 People 🔴 3.8 Attrition 24%, eng morale low
🔄 Operations 🟡 6.0 OKR 65% completion
🔒 Security 🟢 7.8 SOC 2 Type II complete, 0 incidents
📣 Market 🟡 5.5 CAC rising, win rate dropped to 22%
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TOP PRIORITIES
🔴 [1] People: attrition at 24% — engineering velocity will drop in 60 days
Action: CHRO + CEO to run retention audit; target top 5 at-risk this week
🟡 [2] Revenue: pipeline coverage at 1.8x — Q+1 miss risk is high
Action: CRO to add 3 qualified opps within 30 days or shift forecast down
🟡 [3] Engineering: tech debt at 30% of sprint — shipping will slow by Q3
Action: CTO to propose debt sprint plan; COO to protect capacity
WATCH
→ People → Engineering cascade risk if attrition continues (see dimension interactions)
You don't need all metrics to run a diagnostic. The tool handles partial data:
references/health-benchmarks.md — benchmarks by stage (Seed, A, B, C)scripts/health_scorer.py — CLI scoring tool with traffic light outputまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
日本語の概要は準備中です。原文の説明を表示しています。
Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
日本語の概要は準備中です。原文の説明を表示しています。
Mint a tamper-evident, post-quantum-signed receipt for a consequential agent action (deploy, delete, pay, grant-access, model decision) so it can be verified later from the certificate alone. Use when an autonomous agent takes a side-effecting action that may need to be proven later, or when satisfying EU AI Act Article 12 record-keeping. Three decisions: whether an action needs a receipt, minting it, verifying it. Signing is delegated to the open-source OpenAgentOntology package. Not after-the-fact log analysis; not a hosted notary; not a legal opinion.
日本語の概要は準備中です。原文の説明を表示しています。