From spotlight
Manages persistent monitoring for OSINT investigations: scout recommendations to findings.json, creation via coJournalist API, preflight checks, and result ingestion into Spotlight context.
npx claudepluginhub buriedsignals/skills --plugin spotlightThis skill uses the workspace's default tool permissions.
Manage persistent monitoring during and between Spotlight investigations. This skill defines the lifecycle for creating, checking, and ingesting monitoring results.
Orchestrates OSINT investigations: preflight checks search tools and plugins, delegates research to agents, enforces user approval gates, archives findings to Obsidian vaults or directories.
Scans Twitter/X feeds from Anthropic/Claude Code team members for actionable insights on features/updates, tracks state, generates reports using browser automation.
Set up continuous web monitoring with Yutori Scouts. Use when the user wants to track news, competitors, product updates, funding rounds, price changes, or any recurring web information.
Share bugs, ideas, or general feedback.
Manage persistent monitoring during and between Spotlight investigations. This skill defines the lifecycle for creating, checking, and ingesting monitoring results.
topic field set to spotlight:{project} (e.g., spotlight:chat-control-denmark)During execution cycles, agents identify targets worth persistent monitoring. They record structured recommendations in monitoring_recommendations[] in data/findings.json. See references/recommendation-schema.md for the full schema.
Agents recommend when they observe:
Agents do NOT create scouts. They only recommend.
Between investigation cycles, the orchestrator:
monitoring_recommendations[] from data/findings.jsondata/monitoring.jsonSee references/cojournalist-api.md for API patterns.
During preflight of subsequent /spotlight runs, the orchestrator:
data/monitoring.json to find existing scouts for this casetopic)Format:
"Monitoring check — your Page Scout on [target] has returned N new results since your last cycle:
- [date] Summary of result
- [date] Summary of result
These may be relevant to your investigation. Want to review before starting the next cycle?"
If the user wants to use monitoring results, the orchestrator folds relevant information units into the investigation context for the next cycle. The investigator receives them as additional context in the spawn prompt.
See references/source-catalog.md for the full registry of monitoring sources and their capabilities.
Each source has:
data/monitoring.jsonCase-level monitoring state. Created by the orchestrator when the first scout is approved.
{
"topic": "spotlight:{project}",
"scouts": [
{
"name": "Scout display name",
"scout_type": "web|pulse|social|civic",
"topic": "spotlight:{project}",
"created_at": "ISO 8601",
"source_recommendation": "M1",
"source_cycle": 1
}
],
"checks": [
{
"checked_at": "ISO 8601",
"cycle": 2,
"units": [
{
"title": "Human-readable summary",
"source_url": "https://...",
"scout_name": "Scout display name",
"created_at": "ISO 8601"
}
]
}
]
}
| File | Contents |
|---|---|
references/cojournalist-api.md | coJournalist V1 API curl patterns for scout CRUD and unit retrieval |
references/source-catalog.md | Registry of all monitoring sources with capabilities and env vars |
references/recommendation-schema.md | Schema for monitoring_recommendations[] in findings.json |