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 well-organized, appropriately guarded single-file skill: concrete commands for infrastructure OSINT, a mandated authorization gate, a two-source validation rule, and a structured report template. The main gaps are the source-list-only sections that lack executable guidance and the implicit rather than explicit workflow sequencing.
Suggestions
Add one concrete, executable command or query example to the source-list sections — e.g., a HaveIBeenPwned API curl for email breach checks, a Google dork bundle for organization/document OSINT, or an exiftool batch invocation — so Organization, Email/Username, and Threat Intelligence sections match the actionability of the Domain/Infrastructure section.
Make the workflow sequence explicit: number the phases (1. Confirm authorization, 2. Collect per technique, 3. Analyze and cross-validate with two independent sources, 4. Produce the report in the output format) so the sequence does not rely on section ordering alone.
Trim redundant framing: the opening line under the title duplicates the frontmatter description, and generic source-name lists with no usage hint could be tightened or given a one-line 'use for X' purpose each so every token earns its place.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and list-driven with almost no explanation of concepts Claude already knows, but a few tokens could be trimmed — the opening sentence ('Systematically gather, analyze, and correlate publicly available information from open sources') restates the frontmatter description, and some source-name lists (Shodan, Censys, VirusTotal) add little beyond names. It is not 5 because not every token earns its place, and not 3 because the padding is minor. | 4 / 5 |
Actionability | It gives copy-paste-ready commands for whois, dig, the crt.sh curl|jq pipeline, exiftool, and concrete Google dork syntaxes, plus a full markdown report template. However, the Organization, Email/Username, and Threat Intelligence sections are bare source lists with no executable how-to, which keeps it below the 'fully executable, covers common cases' anchor. | 4 / 5 |
Workflow Clarity | The section ordering forms a clear sequence (Authorization check → Collection → Analysis → Output) and includes real validation checkpoints (four-point authorization checklist, 'validate information with at least two independent sources', confidence rating with defined High/Medium/Low levels). It is not 5 because the sequence is implied by section order rather than explicitly enumerated as steps with feedback loops. | 4 / 5 |
Progressive Disclosure | As a single-file skill with no bundle files, everything lives in SKILL.md at an appropriate overview altitude with clear, navigable section headers and no nested references. It is not 5 because at ~120 lines with five collection subsections, per-technique detail (e.g., a source-by-source playbook) is at the boundary of what could be split into reference files, leaving minor organization headroom. | 4 / 5 |
Total | 16 / 20 Passed |