Content
18%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 hollow: it repeats the description three times and provides zero actionable instruction — no commands, code, patterns, or workflow. Its only substance is a link to an external repository, making the skill unusable as written despite a clean section structure.
Suggestions
Replace the filler Instructions section with concrete, executable guidance: actual commands or code patterns for storing, injecting, and checking secrets (e.g. specific CLI invocations and examples).
Delete the verbatim restatements of the description in Overview and When to Use, or make When to Use list concrete trigger conditions instead of repeating the description.
Bundle the detailed guidance from the source repository into local reference files (e.g. references/usage.md) and link to them one level deep instead of punting to an external GitHub URL.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body restates the frontmatter description nearly verbatim three times across Overview, When to Use, and Instructions ('secure environment variable management ensuring secrets are never exposed in claude sessions, terminals, logs, or git commits') — several padded sections with no added value; not anchor 1 since it is not severely verbose in absolute length. | 2 / 5 |
Actionability | No code, commands, steps, or patterns anywhere in the body; the Instructions section only says 'This skill provides guidance and patterns for...' and links to an external repository — entirely vague, describing rather than instructing, an exact match for anchor 1. | 1 / 5 |
Workflow Clarity | No sequence of steps exists at all; there is no workflow to evaluate and no validation checkpoints, matching anchor 1 ('Steps missing or incoherent; no sequence'). | 1 / 5 |
Progressive Disclosure | The body is short with conventionally organized sections (Overview, When to Use, Instructions) and no bundle files to reference, but the only substantive pointer is an external GitHub URL standing in for missing internal content — good structure with a minor organization gap rather than the clear one-level-deep references of anchor 5. | 4 / 5 |
Total | 8 / 20 Passed |