Files included with this skill beyond the listing page.
skill mdSKILL.md2,872 B
History
First seen on skills.sh
First recorded snapshot · 68 installs
SKILL.md
OXYGEN Knowledge Graph
The Knowledge Graph is durable workspace context, not agent memory. Typed company/ICP context and wiki pages ground Tables, copy, Workflows, and Agents with recorded provenance.
Index first
Read the Knowledge index before searching or inventing a slug.
Search for the concept and open the few relevant pages.
Follow wikilinks and backlinks when they materially affect the answer.
Cite the page slugs used.
File durable findings or decisions back into the closest existing page, then append a log entry.
Common gateways are knowledge index, knowledge search, knowledge page get, page upsert/propose, source filing, log append, lint, and synthesis. Hydrate the exact command or MCP schema before writing.
Page model
Slugs are lowercase, stable, human-readable identifiers. Extend an existing slug instead of creating a synonym.
Pages are Markdown with [[wikilinks]]; connect them to durable hubs such as company, ICP, positioning, offers, competitors, campaigns, or learnings.
Sources preserve evidence; pages synthesize it. Do not paste transient run output into canonical prose without judgment.
Revisions and the append-only log make changes inspectable.
Write boundary
Working knowledge—research notes, campaign learnings, operational facts—can be filed as a logged revision. Canonical customer-facing voice, brand, positioning, offer, and pinned playbook changes require a proposal/approval path. Never silently overwrite live copy.
The starter wiki's stub pages can be filled draft-to-active, but canonical claims still follow the proposal gate. Use lint before finalizing structural changes.
Local mirror
knowledge sync provides a disposable filesystem mirror for fast reading and editing. The hosted tenant Knowledge Graph remains authoritative.
Sync before editing.
Push only deliberate changed pages and resolve conflicts explicitly.
Do not treat local files or chat history as a second source of truth.
Use returned revisions and web_url links to verify the hosted result.
Automatic outreach/reply/deal sources may be filed by OXYGEN and synthesized into learnings. Read the source/revision provenance before adopting a generated conclusion as canonical strategy.