Content
40%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 but hollow catalogue stub: it cleanly advertises the skill yet contains none of the actual screenshot workflow, deferring everything to an external repo with only vague install instructions. Its structure is sound, but actionability and workflow clarity are weak because no executable guidance for the skill's stated purpose exists in the bundle.
Suggestions
Inline or bundle the core capture instructions (e.g., the CDP launch flags and a minimal script from the upstream repo) so the skill is actionable without leaving the machine.
Replace the vague "install the upstream bundle into your active agent's skills directory" with concrete, platform-correct commands and exact destination paths, plus a verification step that the skill loads.
Remove the verbatim duplication of the frontmatter description and upstream/category metadata from the body to reclaim tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short with no concept-explanation padding, but it duplicates frontmatter data verbatim: "What it does" restates the description word-for-word and "Source" repeats the upstream URL and category already present in frontmatter. Mostly efficient but includes removable redundancy, fitting the 3 anchor rather than the 4 anchor's 'minor instances'. | 3 / 5 |
Actionability | The only concrete command is `open https://github.com/...` (a macOS command, not executable on Linux), and "install the upstream bundle into your active agent's skills directory" provides no steps, paths, or commands for the actual task. Minimal concrete guidance with high-level hints missing the specific steps to execute — above the 1 anchor because a specific repo and an explicit invocation path (skill name + trigger phrases) are given. | 2 / 5 |
Workflow Clarity | A rough sequence exists (inspect the README, install the upstream bundle, invoke by name or trigger phrase), but every step is undefined: no install commands, no bundle paths, no confirmation the skill is installed and working. This matches 'rough sequence present but many gaps; steps poorly defined'; it is not 3 because the gaps are pervasive, not merely missing validation checkpoints. | 2 / 5 |
Progressive Disclosure | The body is under 50 lines with clear, well-ordered sections and a one-level-deep, clearly signaled pointer to the full workflow. It does not reach 5 because the 'reference' is an external GitHub URL rather than a bundled, loadable file — the actual instructions are unreachable from the skill itself, a minor organization gap. | 4 / 5 |
Total | 11 / 20 Passed |