codehealth-mcp

Real-time structural Code Health via CodeScene MCP — review before edits, verify score deltas after changes, gate commits and PRs. Use when reviewing code quality, refactoring, checking if AI changes degraded a file, or before commit/PR.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, highly actionable, and has an excellent validation-gated workflow. Progressive disclosure is the weak spot: all content lives inline in one file and a referenced config file is missing from the bundle.

Suggestions

Add the referenced mcp-configs/mcp-servers.json template to the bundle so the "copy the codescene entry" instruction resolves to a real file.

Split the detailed score-interpretation and pairing tables into a short reference file (e.g. references/scoring.md) and link to it, keeping SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	Lean and table-driven with no concept explanations Claude already knows; every section (tools, score ranges, feedback loop, pairings) earns its place. Not a 2 because nothing reads as padded or redundant.	3 / 3
Actionability	Concrete tool names, a copy-paste mcpServers JSON block, an AGENTS.md enforcement snippet, and exact before/after workflow steps — fully executable and copy-paste ready.	3 / 3
Workflow Clarity	Clear sequenced feedback loop (review → baseline → change → score → compare → fix-if-regressed → commit safeguard → analyze_change_set) with explicit validation ("Never mark the task done while the score is lower") and a documented MCP-unavailable recovery path.	3 / 3
Progressive Disclosure	Well-organized into sections, but the skill is a ~160-line monolith and references mcp-configs/mcp-servers.json, which is not present in the bundle (references/scripts/assets all absent); a referenced path that does not exist keeps this below the top anchor.	2 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, complete (what + when), and distinctive. Third-person voice is used throughout with no first/second person to penalize.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "review before edits, verify score deltas after changes, gate commits and PRs" — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (structural Code Health review/score/gate) and when via an explicit "Use when..." clause, matching the top anchor.	3 / 3
Trigger Term Quality	Natural user phrasing is well covered: "reviewing code quality, refactoring, checking if AI changes degraded a file, or before commit/PR" — terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	"Real-time structural Code Health via CodeScene MCP" carves a clear niche distinct from generic lint/format skills, with triggers unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/codehealth-mcp/SKILL.md
Commit: 754b8dd

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.