phase-methodology

Orchestrates investigation brief approval and methodology planning with validation gates.

43|8|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/buriedsignals/spotlight --skill phase-methodology-buriedsignals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-methodology
Source: https://github.com/buriedsignals/spotlight/tree/main/skills/phase-methodology
Command: npx skills add https://github.com/buriedsignals/spotlight --skill phase-methodology-buriedsignals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? OSINT investigations often start without a clear scope or an approved plan, leading to unfocused research and unverifiable findings. This Skill structures the first two phases of a Spotlight investigation: a user-approved brief and a validated, tool-grounded methodology before any research begins. ## Core Features & Use Cases - Brief Conversation with Approval Gate: Scrapes lead URLs, asks clarifying questions, and persists the approved direction to brief-directions.txt. - Investigator Planning Spawn: Launches an investigator agent in PLANNING mode that writes methodology.json with tool selections from either the Navigator CLI or a local osint-tools index. - Methodology Validation and Correction: Runs validate-methodology-navigator.py, re-spawns the investigator with bounded correction prompts on failure, and records an attributable approval receipt. - Optional RLM Proposal: On frontier setups, proposes deterministic or hybrid Gemma4 RLM analysis with an explicit opt-in decision recorded in methodology.json. - Use Case: A journalist receives a lead about a Swiss foundation; the Skill scrapes the source URL, confirms scope with the user, spawns a planning agent that selects registry lookup tools, validates the methodology, and gates research until the user approves. ## Quick Start Start a new Spotlight investigation from my lead and walk me through approving the brief and methodology before any research begins.

Frequently Asked Questions about phase-methodology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start an OSINT investigation with an approved methodology?

Provide a lead, URL, or entity to the Spotlight orchestrator. It scrapes any lead URL, asks clarifying questions, gets your brief approval, then spawns an investigator agent that writes methodology.json for your review and approval before research begins.

How does methodology tool selection work without a Navigator subscription?

On local or open-tier deployments, the investigator queries a local osint-tools index with commands like python3 scripts/osint-tools.py find "keywords" --category. No external Navigator call is made, and the methodology records navigator as not required with a fallback reason.

What happens when methodology validation fails?

The methodology is not presented for approval. The investigator agent is re-spawned once with a bounded METHODOLOGY CORRECTION prompt containing the validator errors, and it fixes only methodology.json before validation runs again.

Can I use RLM analysis during methodology planning?

Yes, on frontier setups with integrations.rlm.enabled=true, the Skill proposes deterministic or hybrid Gemma4 E4B RLM before the approval gate. RLM output is treated as leads only, never verified facts, and your opt-in decision is recorded in methodology.json.

Does the methodology approval persist if the brief changes?

No. The approval receipt binds the current brief-directions.txt and methodology.json. If either input changes, the next resolve call returns the methodology gate for re-approval, and any approved RLM run must be regenerated and revalidated.