Content
82%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 lean, highly actionable playbook: concrete greps, ready PoC payloads, explicit validation/negative-control contract, and CVSS scoring, with clear section organization and no bundle-file overhead. The only refinement opportunities are trimming minor rhetorical color in the intro and possibly splitting the payload library and CVSS defaults into reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes competence — no space is spent explaining RAG, CVSS, or embeddings; content is delivered as signal lists, grep commands, tables, and payloads. A few rhetorical flourishes ('the model is one creative prompt away from emitting them verbatim', 'the model dutifully repeats the result') and the two-sentence prioritization intro could be trimmed slightly, matching the 'efficient; minor instances of over-explanation' anchor rather than the score-5 every-token-earns-its-place anchor. | 4 / 5 |
Actionability | Everything is copy-paste ready: four executable grep pipelines for finding retrieval call sites, tenancy filters, and debug echoes; ready-to-send PoC payloads (system-prompt extraction, cross-tenant marker probe, memorisation oracle); concrete success patterns ('sk-[A-Za-z0-9]{20,}', 'BEGIN (PRIVATE|RSA)') and a full CVSS table. This matches the 'fully executable; copy-paste ready; covers common cases' anchor. | 5 / 5 |
Workflow Clarity | Sections are numbered 1–8 in a sensible engagement order (recognise → vectors → audit → exploit → validate → score → chain), and validation is explicit: the validate_finding contract defines negative_command/negative_patterns, and the cross-tenant probe includes a two-run confirmation loop. It stops short of score 5 because the end-to-end sequence is implied by section numbering rather than framed as an explicit ordered procedure, and the validation contract is not wired into a 'fix and re-run' loop — minor gaps matching the score-4 anchor. | 4 / 5 |
Progressive Disclosure | No bundle files (references/, scripts/, assets/) exist and the body references none, so the skill is self-contained; the eight clearly headed sections make navigation easy and the ~130-line playbook is reasonably placed inline. It is not score 5 because some quasi-reference material (the PoC payload library and the default CVSS table) is inlined where a sibling-skills convention of separate payload/CVSS references would fit — 'good structure; most content appropriately placed; minor organization gaps'. | 4 / 5 |
Total | 17 / 20 Passed |