Content
43%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-organized command catalog with mostly executable examples, but it reads as generated CLI documentation rather than a skill: no end-to-end editing workflow is sequenced, validation for destructive operations is missing, one export example is factually wrong, and all detail lives inline with no bundle references. It lands just below the midpoint on workflow clarity and actionability.
Suggestions
Add a sequenced end-to-end workflow example (project new → import → add-track/add-clip → trim/split → export xml) with explicit verification checkpoints, e.g. check the JSON output and confirm the XML file exists after export, since the skill includes destructive operations (remove-clip, --overwrite) that currently lack validation steps.
Fix the invalid export example: 'export render output.pdf --overwrite' uses a nonexistent 'render' subcommand (the Export group only lists 'xml' and 'presets') and names a .pdf output, which a video tool cannot produce; replace it with the actual export command and its real arguments.
Show full command syntax (arguments and flags) for the core timeline/filter commands instead of name-plus-one-line tables, and move the duplicated project-new and REPL examples into a single section — or push the full command catalog to a references/ file, keeping SKILL.md as a lean overview with clearly signaled links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The command tables are mostly lean, but examples repeat (project new and the REPL invocation each appear twice), comments over-explain the obvious ('# Show help'), and time-sensitive version info ('## Version 1.0.0') is stated outside any deprecated/old-patterns section. This fits the 'mostly efficient but could be tightened' anchor rather than 4, where only minor trimming would be needed. | 3 / 5 |
Actionability | There are concrete, executable invocations ('cli-anything-kdenlive --json project info -p project.json'), but the export example is invalid — 'cli-anything-kdenlive --project myproject.json export render output.pdf --overwrite' references a 'render' subcommand that does not exist in the Export group (only 'xml' and 'presets' are listed) and outputs a .pdf from a video editor — and the command tables omit the arguments/flags needed to actually run most commands (e.g. what 'add-clip' or 'trim' take). Not the 4 anchor because the gaps go beyond minor: the core editing workflow has no complete executable example. | 3 / 5 |
Workflow Clarity | No multi-step process is ever sequenced — examples are isolated single commands and the command-group ordering (Project → Bin → Timeline → … → Export) only implies a rough editing sequence. Validation is essentially absent beyond one agent bullet ('Verify outputs exist after export operations') despite destructive/batch operations (remove-clip, remove-track, --overwrite), which caps this dimension; it sits at the 'rough sequence, many gaps, validation absent' anchor rather than 3 because no explicit step list exists at all. | 2 / 5 |
Progressive Disclosure | Sections are well organized with clear headers, but the full command catalog (~150 lines of tables) is inlined rather than split into a reference file, and the only pointers ('See README.md in the package', 'See HARNESS.md in the cli-anything-plugin') reference files outside the skill bundle (no references/ directory exists) and are not navigable links. Matches 'some structure; references present but not clearly signaled; content that should be separate is inline' rather than 4. | 3 / 5 |
Total | 11 / 20 Passed |