debug-cli

Use when users need to debug, modify, or extend the code-forge application's CLI commands, argument parsing, or CLI behavior. This includes adding new commands, fixing CLI bugs, updating command options, or troubleshooting CLI-related issues.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.forge/skills/debug-cli/SKILL.md

Quality

Content

63%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 content is highly actionable with executable commands and a clear iterative debug workflow, but it is notably verbose due to heavy repetition of the same workflow across multiple sections, and it fails to surface the bundled scripts that ship with the skill.

Suggestions

Consolidate the redundant workflow restatements: fold Quick Reference and Tips into the core Workflow section, or move them to a reference file, to remove the 4–5x repetition of build/help/-p/dump/clone.

Link the bundled scripts from the body — e.g. add a "Smoke test" section pointing to `./scripts/test_cli.sh` (described in `scripts/README.md`) instead of re-inlining the same commands.

Promote validation into the workflow as explicit checkpoints (e.g. a "Verify" step using `echo $?` / expected-output checks) rather than leaving exit-code checks as an afterthought in Tips.

Dimension	Reasoning	Score
Conciseness	The same build→--help→-p→dump→clone workflow is restated across the Workflow, Common Testing Patterns, Integration, Quick Reference, and Tips sections, producing several redundant padded blocks that could be consolidated.	2 / 5
Actionability	Commands are fully executable and copy-paste ready with real flags, paths, and example prompts (e.g. "./target/debug/forge -p \"create a hello world rust program\""), covering the common debug cases.	5 / 5
Workflow Clarity	A clear numbered sequence with feedback loops ("Iterate: Repeat until verified", "Keep cloning the source until the fix is verified") is present, but validation checkpoints like exit-code checks are only mentioned in Tips rather than embedded as explicit workflow gates.	4 / 5
Progressive Disclosure	The body is sectioned reasonably, but the provided bundle (scripts/test_cli.sh, scripts/README.md) is never referenced from SKILL.md, and testing-pattern content that could live in a separate file is inlined.	3 / 5
	Total	14 / 20 Passed

Description

92%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 specific, well-triggered, and clearly scoped to the code-forge CLI niche, explicitly answering both what it does and when to use it. Its only weakness is slightly incomplete keyword coverage of CLI terminology variants.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions scoped to the CLI domain — "adding new commands, fixing CLI bugs, updating command options, or troubleshooting CLI-related issues" — giving comprehensive coverage rather than generic verbs.	5 / 5
Completeness	An explicit "Use when users need to debug, modify, or extend..." clause provides concrete triggers, and the "This includes..." sentence clearly states what the skill does.	5 / 5
Trigger Term Quality	Includes natural terms a user would say (debug, CLI commands, argument parsing, troubleshooting), but misses common variants such as "flags", "subcommands", or "args".	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to "the code-forge application's CLI commands, argument parsing, or CLI behavior", creating a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	19 / 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: tailcallhq/forgecode
Path: .forge/skills/debug-cli/SKILL.md
Commit: 6ed5d37

Reviewed: 24 days 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.