CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stackpack-debug

Runtime DevTools for AI agents. Captures terminal output, browser console, build errors, TypeScript errors, git diffs, and screenshots from the running app. MANDATORY for: any bug, error, issue, warning, crash, panic, layout problem, visual glitch, wrong behavior, performance issue, test failure, reviewing the running app, checking app health. Read debug://status FIRST — it's a live situation report. Read debug://errors for errors only. Call debug_investigate for deep analysis.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 excellent actionability and an unusually strong workflow with explicit validation and failure-escalation loops. Its weaknesses are redundancy (repeated instructions, a marketing-style comparison table, duplicated trigger list) and a monolithic structure that inlines reference-grade material instead of splitting it into bundle files.

Suggestions

Remove the 'Why This Beats Manual File Reading' table and state the one rule it supports ('never manually explore code for debugging when the toolkit is available') in a single line; likewise deduplicate the 'Read debug://status FIRST' instruction and the trigger list that repeats the frontmatter description.

Split reference-grade material into bundle files, e.g. references/tools.md for the full per-tool schemas and references/state-telemetry.md for the Loop/network-awareness sections and vite plugin setup, keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

Add concrete call examples for the few tools lacking them (debug_session, debug_patterns) and complete parameter schemas for debug_recall so every tool entry is equally executable.

DimensionReasoningScore

Conciseness

Mostly efficient, but the advocacy table in "Why This Beats Manual File Reading", the "Read debug://status FIRST" instruction repeated three times (section, workflow step 1, Rule 1), and an 18-bullet trigger list duplicating the frontmatter are unnecessary padding.

3 / 5

Actionability

Tool reference gives concrete call shapes with parameters, decision thresholds (">80% confidence", "3+ failures"), and a complete vite.config.ts snippet; minor gaps remain since several tools (debug_session, debug_patterns, debug_recall's full schema) lack examples and most calls are placeholders rather than copy-paste ready.

4 / 5

Workflow Clarity

"The Workflow" is a clear 7-step numbered sequence with explicit validation (debug_verify) and multiple feedback loops: 3+ failures triggers escalation re-investigation, 2+ rejected hypotheses route to debug_patterns, and fileOrbiting flags repeated edits to the same file.

5 / 5

Progressive Disclosure

Well-sectioned single file (~260 lines) with no bundle files at all; the state-telemetry section, vite plugin setup, and detailed per-tool reference are exactly the material that belongs in one-level-deep reference files rather than inlined.

3 / 5

Total

15

/

20

Passed

Description

85%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.

A strong description: concrete capability list, explicit mandatory trigger conditions, and specific entry points. Main weaknesses are a trigger list missing several natural user phrasings and overly broad MANDATORY claims that raise conflict risk with other debugging skills.

DimensionReasoningScore

Specificity

Lists six concrete capture actions ("terminal output, browser console, build errors, TypeScript errors, git diffs, and screenshots") plus specific entry points (debug://status, debug://errors, debug_investigate), giving comprehensive coverage of its stated domain with no notable gaps.

5 / 5

Completeness

Explicitly answers both what ("Captures terminal output, browser console, build errors...") and when ("MANDATORY for: any bug, error, issue, warning, crash...") with concrete trigger phrases, in third-person voice.

5 / 5

Trigger Term Quality

Strong synonym coverage ("bug, error, issue, warning, crash, panic, layout problem, visual glitch, wrong behavior, performance issue, test failure") but common natural variations users say — "fix", "debug", "slow", "broken", "doesn't work" — appear only in the body, not the description.

4 / 5

Distinctiveness Conflict Risk

The runtime-capture niche with named debug_* tools and debug:// resources is distinct, but claiming MANDATORY use for "any bug, error, issue, warning" overlaps with virtually any other debugging or diagnosis skill.

3 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

stackpackdev/debug

Path

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.