---
name: knowledge
description: Use for Signalsurf Knowledge bases, documents, semantic search, saving explicit source material, SOPs, research artifacts, or reusable playbooks.
---

# Signalsurf Knowledge

Read the [shared operating contract](../signalsurf/references/operating-contract.md) unless already loaded; a focused Skill uses the same context, actor, confirmation and result rules.

Knowledge is explicit durable reference content. It is not conversational Memory.

1. Search before creating duplicates with `knowledge_query`; resolve the correct base and document.
2. Use `knowledge_manage` to create a base or save content only when the user wants an explicit durable source/document/playbook.
3. Preserve source, author, dates, and links. Distinguish quoted/observed evidence from synthesis.
4. Do not save private host transcripts, temporary task state, personal preferences, or Project working hypotheses as Knowledge. Route those to private conversation, Memory, or Project Threads as appropriate.
5. A relevant Knowledge document may inform Project work; cite or link it in the Thread rather than copying the entire document.