debug

Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.

Quality

74%

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

Quality

Content

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

A highly actionable debugging reference rich in executable commands, but it suffers from redundancy across sections and over-explains Docker basics. Destructive session-clearing operations lack validation steps, and the long monolithic body would benefit from splitting into reference files.

Suggestions

Consolidate the /home/node/.claude mount guidance into a single section and remove the duplicated "code 1" entry to reduce redundancy.

Add a verification step before destructive session clearing (e.g., confirm the target groupFolder and back up data/sessions before rm -rf).

Move the diagnostic script, SDK Options Reference, and IPC Debugging into separate files under references/ and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly concrete commands, but the /home/node/.claude session-mount point is explained three times (issue #5, Session Persistence, diagnostic script) and "code 1" is covered twice, plus basic Docker concepts (:ro, -v vs --mount) are over-explained.	3 / 5
Actionability	Fully copy-paste-ready docker, grep, and sqlite3 commands with exact mount paths and a complete 8-step diagnostic script covering the common cases.	5 / 5
Workflow Clarity	The diagnostic script provides a validation checklist, but destructive operations (rm -rf data/sessions/, sqlite3 DELETE FROM sessions) are presented without verification checkpoints, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	Good section structure with clear headers, but no bundle files exist and a 350-line monolith inlines content (diagnostic script, SDK options reference, IPC debugging) that would be better split into separate reference files.	3 / 5
	Total	14 / 20 Passed

Description

83%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, third-person description that clearly states both capability and trigger conditions with natural user-facing phrases. It enumerates concrete debugging domains rather than staying abstract, with only minor coverage and synonym gaps.

Dimension	Reasoning	Score
Specificity	Lists several concrete debugging targets ("Covers logs, environment variables, mounts, and common issues") beyond the single action verb "Debug", but stops short of comprehensive action coverage.	4 / 5
Completeness	Explicitly answers both what ("Debug container agent issues… Covers logs, environment variables, mounts") and when ("Use when things aren't working, container fails, authentication problems…") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"things aren't working, container fails, authentication problems" are natural phrases users would say, with good coverage but a few synonyms/extensions missing.	4 / 5
Distinctiveness Conflict Risk	The container-agent niche with triggers like "container fails" is mostly distinct, with only minor overlap risk against general debugging skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jbaruch/nanoclaw-telegram
Path: .claude/skills/debug/SKILL.md
Commit: 7454673

Reviewed: 1 day 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.