Team knowledge management with an agent
Keep reusable organisational notes traceable without turning a shared library into a secret store
Team knowledge management with an agent starts by deciding what belongs in shared memory. The knowledge-base-governance skill classifies each item, checks existing canonical notes and records its source, owner, scope and verification status.
It keeps active project detail in the project repository and reusable guidance in an approved knowledge base. Restricted material stays in its appropriate system; a note may contain a nonsecret retrieval pointer. Stored knowledge remains a discovery aid, so changing facts need fresh checks before consequential reuse.
What it does
- Classify notes before adding them to shared memory
- Record sources, owners and verification dates
- Merge duplicates around one canonical page
- Preserve disputed facts for an owner’s decision
- Separate project state from reusable guidance
- Check volatile claims against authoritative sources
Install and use
- Load the skill in a file-capable agent and approve the knowledge-base directory.
- Provide the note or question and define which material may be stored.
- Ask the agent to read local rules, find existing notes and retain provenance.
- Review confidentiality, unresolved conflicts and canonical links before accepting edits.
FAQ
Source
Made by New Minds Group. Original skill: knowledge-base-governance, published on GitHub under the MIT licence.
View on GitHub