Content
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a lean, well-organized catalogue stub that advertises an upstream skill rather than containing its own substantive instructions, so it scores well on brevity and structure but poorly on actionability because it offloads all concrete guidance to an external repo.
Suggestions
Replace the `open https://...` browser command with an executable clone/inspect command (e.g. `git clone https://github.com/coreyhaines31/marketingskills` plus the exact install path) so the agent can act without manual inspection.
Add a minimal concrete example of the skill's output (e.g. a before/after hook rewrite or a pricing-framing snippet) so the entry is useful even before the upstream bundle is installed.
Turn the 'How to use' prose into an explicit numbered sequence with a verification step (e.g. confirm the skill appears in the agent's skill list after install).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; the only minor redundancy is the 'What it does' section restating the frontmatter description, which does not materially pad the content. | 3 / 3 |
Actionability | The only code block is `open https://github.com/coreyhaines31/marketingskills`, whose own comment concedes it is a starting point ('Inspect the upstream README for exact paths'), and the instruction to 'install the upstream bundle into your active agent's skills directory' gives no concrete command or path, so it describes rather than instructs. | 1 / 3 |
Workflow Clarity | A loose sequence is present in prose (advertise in planning -> install upstream bundle -> invoke by name or trigger), but there are no explicit steps, no validation, and the actual workflow is deferred to the external repo. | 2 / 3 |
Progressive Disclosure | The body is short (under 50 lines) with clearly labeled sections (What it does, Source, How to use) and a single, clearly signaled one-level reference (the upstream repo URL); no bundle files exist locally to misorganize, matching the simple-skill allowance. | 3 / 3 |
Total | 9 / 12 Passed |