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 dense, well-structured offensive-audit skill body: executable recon commands, concrete payloads, explicit finding-validation with negative controls, and ready CVSS vectors, all without tutorial padding. The main improvements are tightening the intro, making the Python PoC runnable, and expressing the audit steps as an explicit ordered sequence.
Suggestions
Make the embedding-inversion Python PoC runnable: import json, define the probe list concretely, and show how LEAKED_EMB and API are supplied.
Convert the audit workflow into an explicitly ordered step sequence (recon -> retrieve call sites -> check tenancy filters -> check ingest gating) so the sequence is stated, not implied by section numbers.
Trim the opening motivational paragraph to one or two sentences.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean: it never explains what embeddings or vector stores are, and attack vectors are described in 2-4 lines each. The two-paragraph motivational intro ("The vector store is the silent half of an LLM application...") is the only trimming candidate — minor over-explanation, matching anchor 4 rather than anchor 5's every-token-earns-its-place. | 4 / 5 |
Actionability | Concrete, copy-paste-ready grep commands for recon, explicit PoC payload strings ("XYZZY-{rand}", the refund injection text), and per-retrieval/per-indexer audit questions. The Python inversion PoC contains placeholders ("probes = [...candidate strings...]", undefined LEAKED_EMB/API, missing import json), which keeps it at anchor 4 (mostly executable, minor gaps) rather than 5. | 4 / 5 |
Workflow Clarity | Sections 1-8 imply a coherent sequence (recognize -> audit -> exploit -> validate -> score -> chain), and the validate_finding contract provides explicit validation with negative controls ("same query from a clean account", "same query before the planted document is indexed"). It sits at anchor 4 rather than 5 because the audit workflow itself is a grep set plus checklists rather than an explicitly ordered step sequence. | 4 / 5 |
Progressive Disclosure | A single-file skill (~156 lines) with no bundle files; content is organized into eight well-labeled sections and everything is appropriately inline at this size. It matches anchor 4 — good structure, minor organization gaps — since the PoC payload set or CVSS tables could be split into reference files if the skill grows. | 4 / 5 |
Total | 16 / 20 Passed |