agentleFS
loganware05loganware05/captains-compass-cursor/.cursor/skills/external-knowledge-ingest/SKILL.md

external-knowledge-ingest

Skill2 starsChanged 32 days agoMITView on GitHub

Ingests Captain-exported Notion and NotebookLM files into Knowledge Steward (explicit CLI)

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Place files under the matching store root:

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

External Knowledge Ingest

Use this Skill when

The Captain has exported Notion pages or NotebookLM learning notes as local files and wants them durable in .agent/knowledge/ for planning readback.

This Skill does not call live Notion MCP or NotebookLM APIs during the default file-export path. For MCP coordination during planning, use Skill notion-integration. For allowlist-gated live ingest after MCP fetch, see Live Notion MCP ingest below.

Live Notion MCP ingest (M15 — Captain local / explicit CLI)

  1. Maintain allowlisted page IDs at .agent/knowledge/notion-allowlist.txt.
  2. Fetch pages via Notion MCP in Cursor; save markdown to .agent/knowledge/external/notion-live/<page-id>.md (or build a JSON payload).
  3. Ingest explicitly:

    ./scripts/ingest-notion-live.sh --source cache
    # offline/CI:
    ./scripts/ingest-notion-live.sh --source fixtures
    # after MCP session payload export:
    ./scripts/ingest-notion-live.sh --source live --payload mcp-pages.json
  4. Items use provenance export_mode: mcp_live (distinct from file exports).

Inputs

  • Markdown exports under .agent/knowledge/external/notion/ or .agent/knowledge/external/notebooklm/
  • Explicit ingest CLI

Procedure

  1. Export content from Notion / NotebookLM to markdown (Captain local).
  2. Place files under the matching store root:

    .agent/knowledge/external/notion/<slug>.md
    .agent/knowledge/external/notebooklm/<slug>.md
  3. Ingest (explicit CLI only):

    ./scripts/ingest-knowledge.sh --from-store notion,notebooklm
  4. Query as kind: knowledge:

    ./scripts/query-knowledge.sh --query "approval gate" --kind knowledge
  5. Items appear in plan Knowledge Context after ingest (informational only).

Output

  • Knowledge items know-notion-* / know-nlm-* with provenance export_mode: file

Prohibited actions

  • Live Notion MCP or NotebookLM network pull as part of ingest
  • Storing approval-critical state only outside the repository
  • Auto-ingest on workstream close
  • Mutating matcher weights from external knowledge

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.