SKILLEMALL.ai
GitHub ↗ RU Sign in

CC osint-investigation

Sparse-clue OSINT investigation methodology for extracting overlooked leads, connecting fragmented evidence, and testing explanations across sources. Use for multi-step CTF challenges, image/video geolocation, event reconstruction, public-account and entity verification, artifact interpretation, infrastructure research, or stalled investigations.

affaan-m/everything-claude-code Agent Skills author: affaan-m MIT 2 files body ≈ 5 561 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Sparse-clue OSINT investigation methodology for extracting overlooked leads, connecting fragmented evidence, and testing explanations across sources.

As a process C 50/100 · Has gaps — References files that are not bundled: ../research-ops/SKILL.md, ../deep-research/SKILL.md, ../exa-search/SKILL.md

AnalyzerInfrastructureMedia and videoResearchtype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
C
50/100
Has gaps
References files that are not bundled: ../research-ops/SKILL.md, ../deep-research/SKILL.md, ../exa-search/SKILL.md
Tools and files w 18
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: osint-investigation (affaan-m/ECC)

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5561 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../research-ops/SKILL.md
  • warning missing-ref reference to a missing file: ../deep-research/SKILL.md
  • warning missing-ref reference to a missing file: ../exa-search/SKILL.md
  • warning missing-ref reference to a missing file: ../security-review/SKILL.md

Process rating: all ten parameters 50/100

Will not run. References files that are not bundled: ../research-ops/SKILL.md, ../deep-research/SKILL.md, ../exa-search/SKILL.md
  • 0Tools and files. 4 referenced file(s) missing: ../research-ops/SKILL.md, ../deep-research/SKILL.md, ../exa-search/SKILL.md
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5561 tokens
  • 85Steps. 34 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +2Single-language instructions
  • +3Description length 348: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 34 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.