CtrlK
BlogDocsLog inGet started
Tessl Logo

chatto-debugging

Production debugging tools for NATS streams, KV buckets, and protobuf events. Covers nats CLI commands, stream inspection, protobuf decoding, and message iteration.

63

Quality

73%

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 ./.agents/skills/chatto-debugging/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

Highly actionable command reference with concrete executable examples, but somewhat padded with rationale prose and monolithic in structure with no external references or sequenced validation checkpoints.

Suggestions

Trim the design rationale ("only supported path...", "leak structural information...") to a single concise note; the full justification for why ConnectRPC omits internals is context Claude does not need to run the commands.

Split "Local Startup And Heap Profiling" into a separate reference file (e.g. references/profiling.md) and link to it from a brief overview section, so SKILL.md stays a clear entry point.

Add a short validation checkpoint before bulk operations, e.g. confirm `nats stream info EVT --json` succeeds and shows messages before running the per-sequence iteration loop.

DimensionReasoningScore

Conciseness

The bulk is lean commands, but rationale prose ("This is the only supported path... it does not expose stream subjects... Those leak structural information...") and project lore ("Past wins came from removing duplicate consumer fanout...") pad the text with context that could be tightened.

2 / 3

Actionability

It provides fully executable, copy-paste-ready commands (nats stream ls/get, base64|protoc decode pipelines, a working for-loop) with concrete example values like EVT, 51, and RUNTIME_STATE, matching the executable-code anchor.

3 / 3

Workflow Clarity

Procedures are organized and each is clear, but it is a command catalog rather than a sequenced multi-step workflow with explicit validation checkpoints or feedback loops, matching the "steps listed but checkpoints missing" anchor.

2 / 3

Progressive Disclosure

No bundle files exist and everything is inline in one ~100-line SKILL.md; the distinct "Local Startup And Heap Profiling" and "NATS CLI" concerns are both inline with no signaled references, matching the "content that should be separate is inline" anchor.

2 / 3

Total

9

/

12

Passed

Description

82%

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 specific, distinctive description with natural trigger terms and concrete actions, held back only by a missing explicit "Use when..." trigger clause. Adding that clause would raise completeness from 2 to 3.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when debugging production NATS streams, KV buckets, or protobuf events, or when you need to inspect stream subjects and per-bucket data."

Include a few common user phrasings in the trigger clause (e.g. "inspect a stream", "decode a protobuf event", "read a KV entry") to broaden natural-language coverage.

DimensionReasoningScore

Specificity

"Covers nats CLI commands, stream inspection, protobuf decoding, and message iteration" lists multiple specific concrete actions, matching the anchor for listing several distinct actions rather than a single vague one.

3 / 3

Completeness

It clearly answers "what" (debugging tools for NATS/KV/protobuf with concrete actions) but has no "Use when..." clause or equivalent explicit trigger guidance, so per the rubric guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

"NATS streams, KV buckets, protobuf events" and "Production debugging" are exactly the natural terms a user debugging this system would say, with good coverage of domain vocabulary rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

The NATS-streams / KV-buckets / protobuf-events debugging niche is sharply specific and unlikely to trigger for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

11

/

12

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
chattocorp/chatto
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.