doctor

System health diagnostics and troubleshooting

Quality

39%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/doctor/SKILL.md

Quality

Discovery

14%

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

This description is too vague and generic to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient specificity to distinguish it from other potential troubleshooting or monitoring skills. The description needs substantial expansion to be useful in a multi-skill environment.

Suggestions

Add specific concrete actions like 'Check CPU/memory usage, analyze log files, identify failing services, diagnose network connectivity issues'

Include a 'Use when...' clause with explicit triggers such as 'Use when the user mentions system errors, slow performance, service failures, or asks to check server health'

Specify the type of system (Linux servers, containers, cloud infrastructure) to reduce conflict risk with other diagnostic skills

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('diagnostics and troubleshooting') without listing any concrete actions. It doesn't specify what diagnostics are performed or what troubleshooting steps are taken.	1 / 3
Completeness	Only weakly addresses 'what' (diagnostics/troubleshooting) and completely lacks any 'when' guidance. No 'Use when...' clause or explicit trigger conditions are provided.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('health', 'diagnostics', 'troubleshooting') that users might say, but misses common variations like 'debug', 'errors', 'logs', 'performance', 'monitoring', or specific system types.	2 / 3
Distinctiveness Conflict Risk	'System health' is extremely generic and could conflict with many skills - server monitoring, application debugging, network diagnostics, database troubleshooting, etc. No clear niche is established.	1 / 3
	Total	5 / 12 Passed

Implementation

64%

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

This is a comprehensive API reference with excellent actionability through concrete, executable code examples and clear command syntax. However, it's overly long for a SKILL.md file, mixing quick-reference material with detailed API documentation that should be split out. The troubleshooting guidance lacks systematic workflow for diagnosing cascading issues.

Suggestions

Split the detailed TypeScript API reference into a separate REFERENCE.md file, keeping only quick-start examples in SKILL.md

Add a diagnostic workflow section showing the recommended sequence for troubleshooting (e.g., 'Start with /doctor quick, if degraded run /doctor <failing-component>, then check Common Issues')

Remove or condense the 'Best Practices' section - these are generic operational practices Claude already understands

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good use of tables and code examples, but includes some unnecessary sections like 'Best Practices' with generic advice Claude already knows, and the 'Common Issues' section explains basic troubleshooting that's fairly obvious from context.	2 / 3
Actionability	Provides fully executable TypeScript code examples that are copy-paste ready, concrete CLI commands, and specific chat commands with clear syntax. All code examples show complete usage patterns with expected outputs.	3 / 3
Workflow Clarity	The skill documents individual checks well but lacks explicit workflow guidance for troubleshooting sequences. There's no clear 'if X fails, then check Y' diagnostic flow or validation checkpoints for resolving issues systematically.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but it's a monolithic document that could benefit from splitting the detailed TypeScript API reference into a separate file. The chat commands, CLI, and API reference could be separate documents linked from a concise overview.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: 2a8c94e

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