health

Aggregate code quality metrics into a weighted 0-10 health score dashboard.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/2300031147/clawopencode --skill health-2300031147
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/2300031147/clawopencode/tree/main/skills/health
Command: npx skills add https://github.com/2300031147/clawopencode --skill health-2300031147

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality information is scattered across tools, dashboards, and reports. This Skill provides a single, automated health dashboard to summarize results.

Core Features & Use Cases

  • Unified health score: Aggregates type-check results, lint signals, test outcomes, dead code detection, and shell hygiene into a single 0-10 score.
  • Trend analysis: Tracks health over time to reveal improvements or regressions.
  • Use Case: Before release, generate a dashboard to surface critical quality issues in one place.

Quick Start

Generate a real-time health snapshot for your repository by running the health skill.

Frequently Asked Questions about health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I aggregate code quality metrics from multiple tools into a single dashboard?

You can aggregate code quality metrics by using a health skill to collect type-checking, linting, test results, and dead code analysis into a unified dashboard. This provides a single automated view to summarize scattered code quality information.

What is a weighted code health score and how does it work?

A weighted code health score computes a 0-10 rating by aggregating results from type-checking, linting, test outcomes, and dead code detection. This scoring mechanism normalizes varied quality signals into a single comparable metric.

Can I track code quality trends over time in my CI workflow?

Yes, you can track code quality trends over time in CI workflows. The health skill applies to desktop and CI environments, recording historical health scores to reveal improvements or regressions across your codebase.

Does this code health monitoring work with linting and type-checking tools?

Yes, code health monitoring works with linting and type-checking tools. The skill aggregates signals from these tools alongside test outcomes and dead code analysis to compute a comprehensive health score.

What's the best way to surface critical code quality issues before a release?

The best way to surface critical code quality issues before a release is to generate a real-time health snapshot. This dashboard aggregates multiple quality tools into one place, highlighting critical issues for immediate action.

What are the limitations of using an aggregated health score for code quality monitoring?

An aggregated health score summarizes issues but may obscure specific tool failures behind a single number. Use it as a high-level indicator alongside detailed reports from individual linting and testing tools to avoid masking critical errors.