Menu
Scoutpost integration for scouts, monitoring, and beat signals via the scout CLI or REST API.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Search, read, link, audit, and journal durable Mycroft or Spotlight knowledge through the storage-neutral Knowledge Workspace Port. Use for vault questions, durable knowledge writes, morning briefs, audits, Spotlight context lookup, approved Spotlight ingestion, OpenKnowledge health checks, legacy QMD/Obsidian migration, and any request that names a knowledge logical space.
Sovereign web search, scrape, and source preservation (SearXNG + Crawl4AI) for Mycroft and Spotlight workflows; Firecrawl is an optional fallback.
Claim-to-evidence grounding discipline for Mycroft skills and recipes. Use when extracting findings, assigning confidence tags, fact-checking claims, ingesting vault notes, or deciding whether a piece of source material is a lead, a partially grounded claim, or a verifiable finding.
Ingest raw material, Spotlight handoffs, URLs, files, and text into the Mycroft knowledge vault.
Fact-check drafts, claims, and source assertions through Mycroft's SIFT recipe, escalating to Spotlight for deeper adversarial review when available. Uses the fact-check profile of epistemic-grounding — emits the full grounding object per the spec.
Eliminate AI-generated writing patterns that erode reader trust. Activate when writing articles, documentation, press releases, or any content where AI patterns would undermine credibility. For journalists using AI assistance who need human-sounding output.
| name | scoutpost |
| description | Scoutpost integration for scouts, monitoring, and beat signals via the scout CLI or REST API. |
Use this skill when Scoutpost was enabled in Mycroft setup. Scoutpost is a monitoring platform for journalists: scheduled scouts watch pages, beats, social profiles, and councils, and extract source-linked information units.
Mycroft talks to Scoutpost over two surfaces — never MCP:
scout CLI — if the scout binary is on $PATH, prefer it. Commands stay visible in the transcript. Its config lives at ~/.scoutpost/config.json.scout is not installed (for example a host with no CLI build), call the hosted API directly.If neither is available, explain what is missing and offer to configure it.
~/.scoutpost/config.json (api_url, supabase_anon_key, api_key) is written by the installer. Run scout directly; never print the key.SCOUTPOST_API_KEY from Goose's secret store or the fallback ~/.config/goose/mycroft/.env. Call https://scoutpost.ai/functions/v1. Send the key as Authorization: Bearer cj_… and the public anon key as the apikey: header — the Edge Functions front door rejects bare bearer tokens.The canonical, product-maintained guide — scout types, verification policy, credit rules — is the hosted product skill:
https://scoutpost.ai/skills/scoutpost.md
Read it for how to operate scouts correctly. This file governs only which surfaces Mycroft uses (CLI or REST — not MCP).
knowledge-workspace into logical space mycroft.