CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-diagnose

Investigate problem, verify findings, and derive solutions

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/recipe-diagnose/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 well-structured, highly actionable diagnosis workflow with concrete prompt templates, explicit validation and feedback loops, and clear checklists. It is token-efficient with only minor dense prose and good internal organization.

DimensionReasoningScore

Conciseness

The body is procedural and operational without explaining concepts Claude already knows, though a few dense passages (e.g. scopeAccounting monotonicity rules) could be tightened.

4 / 5

Actionability

Copy-paste-ready Agent invocation prompts with exact fields, explicit expected-output JSON schemas, enumerated causeCategory values, and complete report templates give fully executable guidance for the common workflow cases.

5 / 5

Workflow Clarity

Steps 0–7 are clearly sequenced with explicit validation checkpoints (Step 2 quality check, Step 3 verification), feedback loops (Step 4 coverage convergence and re-investigation), and completion checklists.

5 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained with clear section/step headers and good navigation; the inline external-skill references (llm-friendly-context, subagents-orchestration-guide) are only loosely signaled.

4 / 5

Total

18

/

20

Passed

Description

38%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 concise and uses correct third-person voice, but it is generic: it names three abstract actions over an unspecified "problem" domain with no trigger guidance, leaving it indistinct from other problem-solving skills.

Suggestions

Add a "Use when..." clause naming concrete triggers users would say, e.g. "Use when diagnosing a bug, finding the root cause of an issue, or troubleshooting a failure."

Pin the domain so the skill is distinguishable, e.g. "Diagnose code or system problems: investigate root cause, verify findings, and derive solutions."

Include natural synonyms/file cues users actually say (debug, diagnose, root cause, troubleshoot) to improve trigger-term quality.

DimensionReasoningScore

Specificity

Names three distinct actions ("Investigate", "verify findings", "derive solutions") but the domain is generic ("problem"), so coverage is concrete in verb form yet not comprehensive or domain-specific.

3 / 5

Completeness

A clear "what" is present (three actions) but there is no "when" / "Use when..." clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"investigate" and "problem" are one or two generic keywords; the natural phrases users actually say (debug, diagnose, root cause, troubleshoot) are missing.

2 / 5

Distinctiveness Conflict Risk

"Investigate problem, verify findings, and derive solutions" is very broad and describes essentially any problem-solving skill, creating high overlap risk with many similar skills.

2 / 5

Total

10

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shinpr/claude-code-workflows
Reviewed

Table of Contents

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.