Content
81%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 strong, dense operational skill: nearly every section is executable, the workflow is explicitly sequenced with a decision gate and manual hit verification, and the non-obvious knowledge (fingerprints, tool invocations, OPSEC boundaries for the PoC) is exactly what a skill should carry. The main improvements are trimming the known-concept explanations in the intro and chains table, showing one concrete provider claim example, and moving the provider fingerprint table to a references/ file.
Suggestions
Move the 25-provider fingerprint table to references/providers.md and reference it from sections 2 and 3, keeping SKILL.md as a lean overview — this would also let the section-3 grep list be generated from one authoritative source instead of a hardcoded subset.
Show one worked claim example (e.g., GitHub Pages: create repo named <user>.github.io, enable Pages, push the marker page) so the payoff step is as concrete as the detection steps, instead of "Deploy via the provider's normal flow".
Tighten the intro paragraph and Section 6 chains table to severity-justifying bullets — Claude already knows cookie scoping, OAuth redirect_uri, and CSP semantics — and cut or compress Section 7's defender signatures if the skill is scoped to offensive/bug-bounty use.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dominated by executable commands and genuinely non-obvious data (fingerprint strings like "There isn't a GitHub Pages site here", "The gods are wise, but do not know of the site which you seek", and tool flags), but a few passages re-explain what Claude already knows: the intro paragraph spelling out cookie/CORS/OAuth/CSP inheritance, and the Section 6 chains table walking through cookie theft, OAuth redirect_uri, and CSP bypass mechanics. This fits anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') rather than level 5, while being far from level 2-3 verbosity. | 4 / 5 |
Actionability | Nearly everything is copy-paste ready: subfinder/amass/dnsx enumeration, a dig-based CNAME extraction loop, curl+grep fingerprint detection, subjack/subzy/nuclei mass-scan invocations, and a heredoc marker page with a proof curl. The one minor gap is the claim step — "Deploy via the provider's normal flow (git push, heroku create, etc.)" defers the actual claim to the upstream reference rather than showing a concrete example for even one common provider (e.g., GitHub Pages). This matches anchor 4 ('mostly executable guidance; concrete code or commands with minor gaps'), just short of level 5's fully covered common cases. | 4 / 5 |
Workflow Clarity | The skill has a clearly numbered pipeline (enumerate → fingerprint → detect → mass-detect → claim → report) with explicit validation and feedback loops: a "Manual sanity check on hits" loop after mass scanning, NXDOMAIN verification at the DNS layer for providers with no body fingerprint, false-positive handling ("Often false positive — verify provider docs before claiming"), and a full Section 8 decision-gate checklist mapping observations to actions including a stop condition when a program forbids takeover testing. This matches anchor 5 ('clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes') — the batch-scan validation guideline is satisfied, so no cap applies. | 5 / 5 |
Progressive Disclosure | The single file is well-organized with numbered, clearly headed sections and only one-level-deep, clearly signaled cross-references (sister skills and the upstream can-i-take-over-xyz repo). However, at ~165 lines with a 25-provider fingerprint table inlined, some content that would fit a references/ file (the provider table, which is reference data rather than workflow instruction) is inline, and no bundle split exists at all. This fits anchor 4 ('good structure; most content appropriately placed; minor organization gaps') rather than the under-50-line simple-skill exception to level 5. | 4 / 5 |
Total | 17 / 20 Passed |