← Back to Skills Marketplace
alirezarezvani

Org Health Diagnostic

by Alireza Rezvani · GitHub ↗ · v2.1.1 · MIT-0
cross-platform ✓ Security Clean
334
Downloads
0
Stars
3
Active Installs
2
Versions
Install in OpenClaw
/install org-health-diagnostic
Description
Cross-functional organizational health check combining signals from all C-suite roles. Scores 8 dimensions on a traffic-light scale with drill-down recommend...
README (SKILL.md)

Org Health Diagnostic

Eight dimensions. Traffic lights. Real benchmarks. Surfaces the problems you don't know you have.

Keywords

org health, organizational health, health diagnostic, health dashboard, health check, company health, functional health, team health, startup health, health scorecard, health assessment, risk dashboard

Quick Start

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:

/health [paste your key metrics or answer prompts]
/health:dimension [financial|revenue|product|engineering|people|ops|security|market]

The 8 Dimensions

1. 💰 Financial Health (CFO)

What it measures: Can we fund operations and invest in growth?

Key metrics:

  • Runway — months at current burn (Green: >12, Yellow: 6-12, Red: \x3C6)
  • Burn multiple — net burn / net new ARR (Green: \x3C1.5x, Yellow: 1.5-2.5x, Red: >2.5x)
  • Gross margin — SaaS target: >65% (Green: >70%, Yellow: 55-70%, Red: \x3C55%)
  • MoM growth rate — contextual by stage (see benchmarks)
  • Revenue concentration — top customer % of ARR (Green: \x3C15%, Yellow: 15-25%, Red: >25%)

2. 📈 Revenue Health (CRO)

What it measures: Are customers staying, growing, and recommending us?

Key metrics:

  • NRR (Net Revenue Retention) — Green: >110%, Yellow: 100-110%, Red: \x3C100%
  • Logo churn rate (annualized) — Green: \x3C5%, Yellow: 5-10%, Red: >10%
  • Pipeline coverage (next quarter) — Green: >3x, Yellow: 2-3x, Red: \x3C2x
  • CAC payback period — Green: \x3C12 months, Yellow: 12-18, Red: >18 months
  • Average ACV trend — directional: growing, flat, declining

3. 🚀 Product Health (CPO)

What it measures: Do customers love and use the product?

Key metrics:

  • NPS — Green: >40, Yellow: 20-40, Red: \x3C20
  • DAU/MAU ratio — engagement proxy (Green: >40%, Yellow: 20-40%, Red: \x3C20%)
  • Core feature adoption — % of users using primary value feature (Green: >60%)
  • Time-to-value — days from signup to first core action (lower is better)
  • Customer satisfaction (CSAT) — Green: >4.2/5, Yellow: 3.5-4.2, Red: \x3C3.5

4. ⚙️ Engineering Health (CTO)

What it measures: Can we ship reliably and sustain velocity?

Key metrics:

  • Deployment frequency — Green: daily, Yellow: weekly, Red: monthly or less
  • Change failure rate — % of deployments causing incidents (Green: \x3C5%, Red: >15%)
  • Mean time to recovery (MTTR) — Green: \x3C1 hour, Yellow: 1-4 hours, Red: >4 hours
  • Tech debt ratio — % of sprint capacity on debt (Green: \x3C20%, Yellow: 20-35%, Red: >35%)
  • Incident frequency — P0/P1 per month (Green: \x3C2, Yellow: 2-5, Red: >5)

5. 👥 People Health (CHRO)

What it measures: Is the team stable, engaged, and growing?

Key metrics:

  • Regrettable attrition (annualized) — Green: \x3C10%, Yellow: 10-20%, Red: >20%
  • Engagement score — (eNPS or similar; Green: >30, Yellow: 0-30, Red: \x3C0)
  • Time-to-fill (avg days) — Green: \x3C45, Yellow: 45-90, Red: >90
  • Manager-to-IC ratio — Green: 1:5–1:8, Yellow: 1:3–1:5 or 1:8–1:12, Red: outside
  • Internal promotion rate — at least 25-30% of senior roles filled internally

6. 🔄 Operational Health (COO)

What it measures: Are we executing our strategy with discipline?

Key metrics:

  • OKR completion rate — % of key results hitting target (Green: >70%, Yellow: 50-70%, Red: \x3C50%)
  • Decision cycle time — days from decision needed to decision made (Green: \x3C48h, Yellow: 48h-1w)
  • Meeting effectiveness — % of meetings with clear outcome (qualitative)
  • Process maturity — level 1-5 scale (see COO advisor)
  • Cross-functional initiative completion — % on time, on scope

7. 🔒 Security Health (CISO)

What it measures: Are we protecting customers and maintaining compliance?

Key metrics:

  • Security incidents (last 90 days) — Green: 0, Yellow: 1-2 minor, Red: 1+ major
  • Compliance status — certifications current/in-progress vs. overdue
  • Vulnerability remediation SLA — % of critical CVEs patched within SLA (Green: 100%)
  • Security training completion — % of team current (Green: >95%)
  • Pen test recency — Green: \x3C12 months, Yellow: 12-24, Red: >24 months

8. 📣 Market Health (CMO)

What it measures: Are we winning in the market and growing efficiently?

Key metrics:

  • CAC trend — improving, flat, or worsening QoQ
  • Organic vs paid lead mix — more organic = healthier (less fragile)
  • Win rate — % of qualified opportunities closed-won (Green: >25%, Yellow: 15-25%, Red: \x3C15%)
  • Competitive win rate — against primary competitors specifically
  • Brand NPS — awareness + preference scores in ICP

Scoring & Traffic Lights

Each dimension is scored 1-10 with traffic light:

  • 🟢 Green (7-10): Healthy — maintain and optimize
  • 🟡 Yellow (4-6): Watch — trend matters; improving or declining?
  • 🔴 Red (1-3): Action required — address within 30 days

Overall Health Score: Weighted average by company stage (see references/health-benchmarks.md for weights).


Dimension Interactions (Why One Problem Creates Another)

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)

Dashboard Output Format

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)

Graceful Degradation

You don't need all metrics to run a diagnostic. The tool handles partial data:

  • Missing metric → excluded from score, flagged as "[data needed]"
  • Score still valid for available dimensions
  • Report flags which gaps to fill for next cycle

References

  • references/health-benchmarks.md — benchmarks by stage (Seed, A, B, C)
  • scripts/health_scorer.py — CLI scoring tool with traffic light output
Usage Guidance
This skill appears coherent and implements a local organizational-health scorer. Before installing/running: (1) review the remainder of the Python script (only a truncated portion was shown here) to ensure there are no hidden network calls or unexpected filesystem access; (2) run it locally in a controlled environment if you will supply sensitive internal metrics; (3) confirm you have a Python runtime available (the script claims to use only the stdlib); (4) if you plan to integrate it with other systems (CI, dashboards, or chatbots), expect to add connectors that may require credentials — only supply those to trusted code. Overall, nothing here requests unrelated privileges or secrets.
Capability Analysis
Type: OpenClaw Skill Name: org-health-diagnostic Version: 2.1.1 The skill bundle is a legitimate organizational health diagnostic tool that calculates business metrics across eight dimensions. The Python script (health_scorer.py) uses only standard libraries, contains no network or file system access, and performs transparent scoring logic based on user-provided or sample data. The documentation (SKILL.md and health-benchmarks.md) is purely informational and lacks any prompt-injection attempts or malicious instructions.
Capability Assessment
Purpose & Capability
Name/description match the provided materials: SKILL.md describes an 8-dimension org-health diagnostic and the repository contains a health_scorer.py and benchmark reference material that implement that functionality. No environment variables, external services, or unrelated binaries are requested.
Instruction Scope
Runtime instructions tell the agent/user to run the local Python script or paste metrics; they do not instruct reading unrelated system files, sending data to external endpoints, or accessing credentials. The guidance to use slash-like commands (/health) appears to be an input convention, not an instruction to contact external services.
Install Mechanism
There is no install spec and the Python script claims to be stdlib-only. No archives or external downloads are requested. Running the tool requires only a Python runtime, which is proportional to the stated purpose.
Credentials
The skill declares no required env vars, no primary credential, and no config paths. The code and docs do not reference secrets or external API keys. This is proportional to a local scoring/diagnostic tool.
Persistence & Privilege
The skill is not forced-always, and there's no install script or requests to modify agent/system-wide configuration. Autonomous model invocation is allowed by platform defaults but this skill does not request elevated persistence or cross-skill config changes.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install org-health-diagnostic
  3. After installation, invoke the skill by name or use /org-health-diagnostic
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.1.1
v2.1.1: optimization, reference splits
v1.0.0
Initial release.
Metadata
Slug org-health-diagnostic
Version 2.1.1
License MIT-0
All-time Installs 3
Active Installs 3
Total Versions 2
Frequently Asked Questions

What is Org Health Diagnostic?

Cross-functional organizational health check combining signals from all C-suite roles. Scores 8 dimensions on a traffic-light scale with drill-down recommend... It is an AI Agent Skill for Claude Code / OpenClaw, with 334 downloads so far.

How do I install Org Health Diagnostic?

Run "/install org-health-diagnostic" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Org Health Diagnostic free?

Yes, Org Health Diagnostic is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Org Health Diagnostic support?

Org Health Diagnostic is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Org Health Diagnostic?

It is built and maintained by Alireza Rezvani (@alirezarezvani); the current version is v2.1.1.

💬 Comments