knowledge-base

Organizes markdown knowledge bases using a three-layer source-grounded workflow.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/jcafeitosa/anxionOS --skill knowledge-base-jcafeitosa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-base
Source: https://github.com/jcafeitosa/anxionOS/tree/main/.cursor/skills/knowledge-base
Command: npx skills add https://github.com/jcafeitosa/anxionOS --skill knowledge-base-jcafeitosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining a knowledge base manually fails because bookkeeping — preserving sources, cross-linking pages, tracking superseded notes — costs more effort than the value it returns. This Skill encodes the layer model, folder rules, status flows, and log discipline so an agent can run the ingest → research → consolidate loop without losing the evidence chain. ## Core Features & Use Cases - Three-layer layout: Governs external-sources/ (verbatim raw sources), research/ (provisional draft analysis), and articles/ (canonical stable knowledge) with per-folder rules. - Status and supersedes flows: Tracks status: draft → stable transitions and maintains supersedes: / superseded_by: chains so every claim traces back to a preserved source. - Log discipline: Requires one dated log.md entry per content-changing turn, with markdown links so entries register in the knowledge graph's backlinks. - Use Case: A user shares a URL; the agent ingests it verbatim into external-sources/, drafts a sourced research note, and after a team decision consolidates a canonical article that supersedes the research — all logged and linked. ## Quick Start Ask the agent to ingest a shared URL into the knowledge base and then research the topic using the preserved sources.

Frequently Asked Questions about knowledge-base

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

FAQPage Schema
How do I structure a source-grounded knowledge base?▼

Use three layers: external-sources/ holds raw sources saved verbatim, research/ holds provisional draft analysis citing those sources, and articles/ holds canonical stable knowledge committed after a decision. Every downstream claim must trace back to a preserved source.

How do I promote research notes to canonical articles?▼

Run the consolidate procedure via the sibling consolidate-notes skill once a decision is made. It creates an article with status: stable, adds a supersedes chain pointing to the research docs, and marks those research docs as deprecated with superseded_by links.

Does this knowledge base workflow require a specific platform?▼

Yes, it requires an agent host with the OpenKnowledge MCP server configured, and it is installed project-local via ok seed --pack knowledge-base. It complements the platform open-knowledge skill rather than replacing it.

Why must sources be saved verbatim instead of linked?▼

Saving fetched text, PDF extracts, and file copies verbatim in external-sources/ protects the knowledge base from link rot. Citing local paths instead of bare URLs keeps the full evidence chain traceable inside the repository.

What happens if I skip the log.md entry after editing?▼

Skipping the dated log entry breaks the audit trail, since one entry per content-changing turn is mandatory. Entries must reference docs as markdown links so they register in the knowledge graph's backlinks.