doctor

System health diagnostics and troubleshooting

Quality

53%

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

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/doctor/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

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

The body is a thorough, mostly executable API reference with good section structure and minimal concept-padding, but it inlines the full reference rather than progressively disclosing it to bundle files and provides no sequenced troubleshooting workflow with validation checkpoints. It is strong on actionability but weaker on workflow clarity and progressive disclosure.

Suggestions

Move the bulk per-check API reference into a references/ file (e.g. REFERENCE.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

Add an explicit diagnostic workflow with validation checkpoints (run diagnostics → review failing checks → apply fix from Common Issues → re-run to verify), especially since troubleshooting is inherently iterative.

Trim the repetitive per-check console.log formatting examples into a single shared pattern to recover token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (code and tables, little concept-padding Claude already knows), but ~260 lines with seven near-identical per-check console.log blocks could be tightened, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Concrete executable TypeScript (createDoctorService, runDiagnostics, checkSystem, etc.) and CLI commands cover the common cases, but examples illustrate output logging rather than complete end-to-end programs, leaving minor gaps below the fully copy-paste-ready 5.	4 / 5
Workflow Clarity	This is a reference catalog rather than a sequenced diagnostic/troubleshooting workflow; an implied run-then-review sequence exists but there are no explicit validate→fix→retry checkpoints, matching 'sequence present but checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	Section headers organize the content well, but the entire API reference (all per-check code blocks) is inlined into SKILL.md with no bundle files and no clearly signaled external references, fitting 'some structure but content that should be separate is inline'.	3 / 5
	Total	13 / 20 Passed

Description

50%Weight 40%Scale 1-5

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 accurate and on-domain but terse and generic, naming the system-health niche and two high-level actions without any explicit usage trigger. It meets the bar for a usable description but stops short of the concrete, trigger-rich phrasing that would maximize discoverability.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when the user wants to check system health, run diagnostics, or troubleshoot node/network/database/channel issues.'

Enumerate concrete actions (e.g. 'runs system, node, network, API, database, and channel checks; reports healthy/degraded/unhealthy status') to lift specificity and trigger coverage.

Include natural synonyms users say ('check health', 'monitor', 'debug', 'diagnose') to widen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('system health') and two actions ('diagnostics', 'troubleshooting'), matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor; the actions themselves are generic, so it does not reach 4.	3 / 5
Completeness	It gives a clear 'what' (system health diagnostics and troubleshooting) but no 'Use when...' trigger clause; the rubric caps completeness at 3 when explicit trigger guidance is absent.	3 / 5
Trigger Term Quality	'diagnostics', 'troubleshooting', and 'health' are natural user terms, but common variations like 'check', 'monitor', or 'debug' are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'System health' carves a recognizable niche, but 'troubleshooting' is broad and could overlap with general debugging skills, fitting the 'somewhat specific but could still overlap' anchor.	3 / 5
	Total	12 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/doctor/SKILL.md
Commit: 715fd4a

Reviewed: 4 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.