phase-ingest

Manages the ingestion phase of Spotlight investigations by confirming and executing knowledge vault ingestion.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? At the end of a Spotlight OSINT investigation, verified findings need to be safely transferred into the journalist's knowledge vault without accidental duplication or unconfirmed writes. This Skill governs that final ingestion phase with a resolver-driven state machine and explicit user confirmation. ## Core Features & Use Cases - Resolver-owned state transitions: Enters only from a spotlight_resolve result with phase: ingest, following resume.state and resume.resume_at instead of inspecting ingestion.json directly. - User confirmation gate: Displays an AI assistance notice and asks the user whether to ingest confirmed findings before any write occurs, recording declined decisions durably. - Idempotent ingestion lifecycle: Handles pending, requested, completed, and seal substeps so the ingest skill is invoked exactly once and the projection receipt is sealed via spotlight_transition. - Use Case: After an investigation completes, the orchestrator resolves into the ingest phase; this Skill asks the journalist for confirmation, invokes ingestion with the project path and vault config from .spotlight-config.json, then seals the receipt to end the pipeline. ## Quick Start Resolve the completed Spotlight investigation into the ingest phase and confirm whether the verified findings should be ingested into the knowledge vault.

Frequently Asked Questions about phase-ingest

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

FAQPage Schema
How do I ingest Spotlight investigation findings into the knowledge vault?▼

Resolve the completed case into the ingest phase, confirm ingestion when prompted, and the phase invokes the ingest skill with the project path and vault config from .spotlight-config.json. After the receipt is written, the phase seals it via spotlight_transition.

What happens if I decline ingestion in Spotlight?▼

The phase calls spotlight_transition with the decideIngest operation and a declined payload. The resolver writes a declined marker and a hash-bound decision, so the choice is durable and the pipeline ends without writing to the vault.

Can ingestion run twice on the same Spotlight case?▼

No. Once the human decision is durable, the phase does not ask again, and after the ingest skill writes its completed receipt the phase seals it instead of invoking ingestion a second time.

Why does the phase not read ingestion.json directly?▼

State ownership belongs to the resolver. The phase follows the resume.state and resume.resume_at fields returned by spotlight_resolve, which prevents inconsistent substep selection from inspecting raw files.