Content
75%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.
A well-organized, actionable single-file skill: concrete CLI commands, named MCP tools, and example workflows with implicit feedback loops. The main gaps are stylized non-executable MCP call syntax, verification stated as advice rather than workflow steps, and slight redundancy between the description and the body's opening sections.
Suggestions
Replace the stylized [claude_prompt] blocks with a literal, executable invocation example (actual tool-call arguments or CLI flags) so the MCP path is as copy-paste-ready as the CLI path.
Fold 'Check Results' into each example workflow as an explicit validation step (review output, then proceed/continue) to upgrade the implicit feedback loop to an explicit one.
Trim the intro sentence and When-to-Use list that restate the frontmatter description, or move the MCP configuration JSON blocks to a reference file to reduce inline tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient: terse best practices ("Capture Session IDs: Save session IDs from responses to resume conversations"), compact error handling, and code examples with no explanation of concepts Claude already knows. It falls short of anchor 5 because the intro line "Delegate coding tasks to Claude Code CLI from any context" and the When-to-Use list largely restate the frontmatter description, and the three example workflows add tokens with marginal new information. It is above anchor 3 because there is no real over-explanation to strip. | 4 / 5 |
Actionability | Mostly executable: concrete CLI commands with flags ("claude -p \"List all TODO comments in this project\" --output-format json", --continue, --resume <session-id>), named MCP tools, and complete MCP config JSON blocks. It is not anchor 5 because the MCP invocation examples use stylized pseudo-syntax ([claude_prompt] blocks with prompt:/working_dir: fields) rather than copy-paste-ready tool calls, and the Rust example depends on an unverified claude_code_rs crate. It is well above anchor 3 since the CLI path is fully executable. | 4 / 5 |
Workflow Clarity | Example workflows give clear sequences, including a two-step followup pattern (identify deprecated API uses, then "Now migrate the first 3 files you found to API v2" after reviewing results), and Best Practices embed checkpoints like "Check Results: Verify Claude Code's output before proceeding" and "Capture Session IDs". Not anchor 5 because verification is stated as a bullet rather than an explicit validate-before-proceeding step woven into each workflow; not anchor 3 because checkpoints and sequences are present, only implicitly ordered. | 4 / 5 |
Progressive Disclosure | Good structure with well-labeled sections (When to Use, Usage Patterns, Configuration, Best Practices, Example Workflows, Error Handling) and no dead or nested references — appropriate for a single-file skill with no bundle. It misses anchor 5 because at ~130 lines it exceeds the simple-skill threshold and content such as the two host-specific MCP config blocks and the example workflows could plausibly live in reference files; it is above anchor 3 because nothing is buried and navigation is easy. | 4 / 5 |
Total | 16 / 20 Passed |