CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

debug

Debug issues by investigating logs, database state, and git history

Quality

72%

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 ./.claude/skills/debug/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 delivers a clear, gated investigation workflow with concrete, executable commands and well-structured sections. Its weaknesses are token redundancy — duplicated command blocks, scripted dialogue, and a repetitive closing line — plus slightly vague discovery guidance for log and database locations.

Suggestions

Remove the Quick Reference section's duplicated commands (git, sqlite3, ps/lsof appear verbatim in the Step 2 task prompts) or keep only the Quick Reference and strip them from the task blocks.

Replace the two scripted 'Initial Response' dialogue blocks with a short 2-3 line summary of what to ask the user in each invocation mode.

Delete the closing 'Remember:' paragraph, which restates the intro, and add guidance for handling inconclusive task results (e.g., cross-check logs against git timing before presenting a root cause).

DimensionReasoningScore

Conciseness

The core process guidance is lean and free of concept over-explanation, but the Quick Reference repeats commands verbatim from the Step 2 task blocks, the 'Initial Response' section scripts ~25 lines of dialogue, and the closing 'Remember:' paragraph restates the intro. Mostly efficient but could be tightened, matching anchor 3.

3 / 5

Actionability

Commands like 'ls -t ./logs/*.log | head -1', 'sqlite3 {database_path} ".tables"', 'git log --oneline -10', and 'lsof -i :{port}' are copy-paste ready, and each task prompt has numbered steps plus an explicit 'Return:' contract. Minor gaps remain: log and database locations are deferred to 'check project-specific locations'/'check project config', keeping it just short of fully executable.

4 / 5

Workflow Clarity

A clear three-step sequence (understand, investigate, report) with an explicit gate ('Always require problem description', Step 1 fires only after the user describes the issue) and fallback guidance ('If That Doesn't Work'). Validation gaps are minor — no instruction to cross-check task findings against each other or handle empty/inconclusive task results — matching anchor 4 rather than the explicit-feedback-loop anchor 5.

4 / 5

Progressive Disclosure

No bundle files exist and none are referenced; the ~190-line body is well-organized into clear sections (Initial Response, Environment, Process Steps, Important Notes, Quick Reference) with no nested or buried references. Structure is good with minor gaps from inter-section duplication; it exceeds the under-50-line simple-skill exception, so not a 5.

4 / 5

Total

15

/

20

Passed

Description

62%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 states clear, concrete capabilities with natural trigger keywords, but entirely lacks a 'when to use' clause, capping completeness. Adding an explicit 'Use when...' sentence with trigger variations (troubleshooting, errors, stack traces) would lift both completeness and trigger coverage.

Suggestions

Add a 'Use when...' clause (e.g., 'Use when the user hits an error or unexpected behavior during testing or implementation and asks to debug or troubleshoot it') to fix the completeness cap.

Include natural synonyms such as 'troubleshoot', 'errors', or 'stack traces' alongside 'debug' to broaden trigger-term coverage.

Sharpen distinctiveness by naming the read-only, no-edit investigation scope (e.g., 'investigates without editing files') to separate it from fix/refactor skills.

DimensionReasoningScore

Specificity

The phrase 'investigating logs, database state, and git history' names three concrete investigation actions with only minor gaps in coverage (e.g., service/process checks covered in the body are absent). It lists several specific actions like the anchor-4 example, but is not comprehensive enough for a 5.

4 / 5

Completeness

It clearly answers 'what' ('Debug issues by investigating logs, database state, and git history') but contains no 'Use when...' clause or equivalent explicit trigger guidance, which the guidelines cap at 3.

3 / 5

Trigger Term Quality

'Debug', 'logs', 'database state', and 'git history' are terms users would naturally say when hitting a problem. Common variations like 'troubleshoot', 'error', or 'stack trace' are missing, so it falls short of comprehensive synonym coverage (5).

4 / 5

Distinctiveness Conflict Risk

'Debug issues' is a broad trigger that could overlap with general troubleshooting or code-analysis skills, even though the logs/database/git niche adds some specificity. It is somewhat specific but could still overlap with similar skills, matching anchor 3 rather than the mostly-distinct anchor 4.

3 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/debug/SKILL.md

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.