cli-anything-audacity

Command-line interface for Audacity - A stateful command-line interface for audio editing, following the same patterns as the GIMP and Ble...

Quality

46%

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 ./audacity/agent-harness/cli_anything/audacity/skills/SKILL.md

Quality

Content

62%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 a well-organized, mostly actionable reference for the Audacity CLI, but it lacks an explicit multi-step workflow with validation checkpoints for the destructive render/export step, and its external references are weakly signaled. The export example also appears to contain an incorrect file extension and flag.

Suggestions

Add an explicit end-to-end workflow with a validation checkpoint for export, e.g. create project -> add tracks/clips -> apply effects -> `export render` -> `media check`/verify the output file exists before declaring success.

Fix the Export example: replace `export render output.pdf --overwrite` with a real audio output (e.g. `output.wav`/`output.mp3`) and the documented project flag (`-p myproject.json`) to match the command tables.

Convert the inlined per-group command tables into clearly signaled one-level-deep references (e.g. 'Full command reference: See REFERENCE.md') if bundle files exist, or state explicitly that this is the complete reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference material (command tables and short examples) with little concept-explanation padding; the only slack is the 'For AI Agents' list and State Management section restating things already shown via examples.	4 / 5
Actionability	It provides concrete, executable commands (e.g. `cli-anything-audacity project new -o myproject.json`, `--json project info`) and a full command table, but the export example uses a likely-wrong `.pdf` output and `--project` flag inconsistent with the documented `-p`, leaving a minor gap.	4 / 5
Workflow Clarity	Sequences are present as grouped command examples but there is no end-to-end workflow with validation checkpoints; since rendering/export is a batch+destructive operation and the only validation guidance is the generic 'verify outputs exist after export', the feedback-loop cap applies and holds this at 3.	3 / 5
Progressive Disclosure	Structure is reasonable with clearly headed sections, but the large command-group tables are inlined in SKILL.md and the external pointers (README.md, TEST.md, HARNESS.md) are vaguely referenced as 'in the package' rather than as one-level-deep bundle links, so organization is only moderate.	3 / 5
	Total	14 / 20 Passed

Description

30%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 identifies the tool and domain but is thin on concrete capabilities and entirely lacks a 'Use when...' trigger clause, capping completeness low. It also repeats 'command-line interface' twice, which is padding rather than information.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user wants to edit audio, mix tracks, apply effects, or render projects in Audacity.'

List 2-3 concrete actions (import/add clips, apply effects, render/export audio) instead of the generic 'command-line interface for audio editing'.

Remove the redundant second 'A stateful command-line interface...' clause or fold 'stateful' into a single concise sentence to cut padding.

Dimension	Reasoning	Score
Specificity	The description names the domain (Audacity audio editing CLI) but the only 'action' stated is 'command-line interface for audio editing', which is generic; no concrete actions like importing clips, applying effects, or rendering are listed.	2 / 5
Completeness	It states a vague 'what' (a CLI for audio editing) and has no 'Use when...' trigger clause at all, so the 'when' is entirely missing, placing it at the low end of the completeness scale.	2 / 5
Trigger Term Quality	It surfaces 'Audacity', 'audio editing', and 'command-line interface', but omits natural user phrasings like 'mix audio', 'apply effects', 'export/render audio', or file extensions; the trigger terms are technical and sparse.	2 / 5
Distinctiveness Conflict Risk	Naming Audacity and the specific cli-anything pattern gives it a recognizable niche, but 'audio editing' generically overlaps with other audio skills and there is no trigger phrase to distinguish usage context.	3 / 5
	Total	9 / 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: HKUDS/CLI-Anything
Path: audacity/agent-harness/cli_anything/audacity/skills/SKILL.md
Commit: 34f5195

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.