monitoring

Convert investigation findings into user-approved monitoring recommendations handed off to Mycroft.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Investigations often surface targets worth watching after a case closes, but ad-hoc monitoring setup risks unapproved actions, leaked credentials, and scattered state. This Skill turns findings into explicit, user-approved monitoring recommendations while keeping Spotlight out of live monitoring operations. ## Core Features & Use Cases - Structured Recommendations: Records targets, rationale, priority, and criteria in monitoring_recommendations[] inside data/findings.json using a defined schema. - Approval-Gated Handoff: Presents recommendations to the user and, only after explicit approval, hands them to Mycroft in plain language for any Scoutpost scout creation. - Sensitive Mode Guardrails: In sensitive mode, records recommendations only and blocks external handoff unless the user explicitly resumes it. - Use Case: After fact-checking reveals a procurement page changed twice during an investigation, the Skill logs a high-priority web monitoring recommendation and asks the user whether to hand it to Mycroft for a durable monitor. ## Quick Start Ask the orchestrator to review the current case findings and propose monitoring recommendations for any targets worth watching.

Frequently Asked Questions about monitoring

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

FAQPage Schema
How do I turn investigation findings into monitoring recommendations?▼

Record each target in the monitoring_recommendations array of data/findings.json with an id, target, scout_type, criteria, rationale, priority, and finding_refs. The orchestrator then presents these to the user for explicit approval before any handoff.

What monitoring types does the recommendation schema support?▼

The schema supports four scout_type values: web, pulse, social, and civic. Social recommendations add platform and monitor_mode fields, while pulse and civic recommendations add location, root_domain, or tracked_urls fields.

Does Spotlight create Scoutpost scouts or monitors directly?▼

No. Spotlight never installs Scoutpost, reads its credentials, creates scouts, or stores scout identifiers. After user approval, it hands the recommendation to Mycroft in plain language, and Mycroft owns authentication and durable monitor state.

When should I skip monitoring recommendations entirely?▼

Skip recommendations when the source is static and unlikely to change, when the investigation covers a closed historical event, or when the case is ending with no useful follow-up watch.

What happens to monitoring recommendations in sensitive mode?▼

In sensitive mode, recommendations are recorded in the case file only. Nothing is handed to an external monitoring system unless the user explicitly resumes that choice later.