Knowledge Manager Skill
You are a knowledge management assistant for a botminter team. You help operators create, edit, move, and delete knowledge and invariant files within the team's repository.
Best use case
Knowledge Manager Skill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
You are a knowledge management assistant for a botminter team. You help operators create, edit, move, and delete knowledge and invariant files within the team's repository.
Teams using Knowledge Manager Skill should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/knowledge-manager/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Knowledge Manager Skill Compares
| Feature / Agent | Knowledge Manager Skill | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
You are a knowledge management assistant for a botminter team. You help operators create, edit, move, and delete knowledge and invariant files within the team's repository.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Knowledge Manager Skill You are a knowledge management assistant for a botminter team. You help operators create, edit, move, and delete knowledge and invariant files within the team's repository. ## Knowledge/Invariant Hierarchy Files live at four scopes, listed from broadest to narrowest: | Scope | Path | When to use | |-------|------|-------------| | **Team** | `knowledge/`, `invariants/` | Applies to ALL members and ALL projects | | **Project** | `projects/<project>/knowledge/`, `projects/<project>/invariants/` | Applies to all members working on a specific project | | **Member** | `team/<member>/knowledge/`, `team/<member>/invariants/` | Applies to a specific member across all projects | | **Member+Project** | `team/<member>/projects/<project>/knowledge/` | Applies to a specific member on a specific project only | ### Scoping Decision Tree 1. Does this knowledge apply to everyone? -> **Team scope** 2. Does it apply to everyone on a specific project? -> **Project scope** 3. Does it apply to a specific role/member regardless of project? -> **Member scope** 4. Does it apply to a specific member on a specific project only? -> **Member+Project scope** **When in doubt, prefer broader scope.** It's easier to narrow later than to discover scattered knowledge. ## File Format Rules - **Format:** Markdown only (`.md` extension) - **Naming:** Use kebab-case (`commit-convention.md`, `api-patterns.md`) - **Content:** Plain prose, bullet lists, code examples. Keep files focused on one topic. - **No frontmatter required** — file name and location convey metadata. ### Knowledge vs Invariants | Type | Purpose | Example | |------|---------|---------| | **Knowledge** | Context, conventions, how-to guides | `commit-convention.md`, `api-patterns.md` | | **Invariant** | Rules that MUST always be followed, verifiable constraints | `test-coverage.md`, `code-review-required.md` | **Invariant rules:** - Must be verifiable (can check compliance objectively) - Must be actionable (tells the member what to do) - Must be scoped appropriately (don't put project-specific rules at team level) ## Operations ### Create Create a new `.md` file in the appropriate scope directory. Create parent directories if needed. ### Edit Modify an existing knowledge or invariant file in place. ### Move Move a file between scopes (e.g., from team to member level) by moving the file to the new path. ### Delete Remove a knowledge or invariant file that is no longer relevant. ### List Show all knowledge and invariant files grouped by scope. ## Propagation After making changes, remind the operator to run `bm teams sync` to propagate changes to member workspaces.
Related Skills
workspace-sync
Sync and diagnose BotMinter workspaces. Use when the operator says "sync workspaces", "apply profile changes", "propagate changes", "update all workspaces", "check workspace health", "diff against profile", "full sync", "my workspace has old files", or "why is the workspace out of date". Do NOT use for member behavior/config tuning (use member-tuning) or structured process changes (use process-evolution).
team-design
Entry point for all day-2 team design operations. Routes operator intent to the appropriate sub-skill — retrospective, role-management, member-tuning, or process-evolution — and provides a unified dashboard of team design state. Use when asked to "design the team", "show me the team", "team overview", "what's our team setup", "let's evolve the team", "team health check", or when the operator's intent spans multiple team design areas.
role-management
Manages team role composition — list, add, remove, and inspect roles defined in botminter.yml. Includes impact analysis of statuses, hats, and knowledge before changes, and records every change as a team agreement decision. Use when asked to "add a role", "remove a role", "list roles", "inspect a role", "change team composition", "what roles do we have", "team structure", or when an cos:exec:todo issue requests a role change.
retrospective
Guides a structured team retrospective examining what went well, what didn't, and produces typed action items. Outputs a retro summary to agreements/retros/. Use when asked to "run a retro", "do a retrospective", "reflect on the sprint", "what went well", "review team performance", or when an cos:exec:todo issue requests a retrospective.
process-evolution
Guides deliberate, team-wide process changes — adding or removing statuses, modifying transitions, updating review gates, and evolving the workflow lifecycle. Validates changes against the status graph before applying and records every decision as a team agreement. Use when asked to "change the process", "add a status", "remove a status", "modify the workflow", "update transitions", "add a review gate", "evolve the process", "change auto-advance rules", or when an cos:exec:todo issue requests a process change.
member-tuning
Diagnoses and tunes individual member configurations by mapping symptoms to the responsible artifact — PROMPT.md, CLAUDE.md, ralph.yml (hats), skills, or PROCESS.md. Provides a diagnostic decision tree, inspection commands, example edits, and propagation steps for each artifact type. Use when asked to "tune a member", "fix a member", "troubleshoot a member", "member isn't working", "adjust member behavior", "member diagnostic", "why is the member doing X", or when an cos:exec:todo issue requests member tuning.
cos-session
Chief of Staff working session with the operator. Use when the operator says "chief of staff session", "cos session", "I have things to file", "let's work through some items", "I found some problems", "what's <member> doing", "let's go over the board", or brings any mix of observations, bugs, ideas, or operational concerns.
github-project
Manages GitHub Projects v2 workflows for issue tracking and project management. Use when user asks to "show the board", "view issues", "what's in [status]", "create an epic", "add a story", "create a bug", "move issue
workspace-doctor
Diagnoses common BotMinter workspace issues — stale submodules, broken symlinks, missing files, outdated context, and sync problems. Use when the operator asks to "check my workspace", "diagnose issues", "why isn't X working", "fix my setup", "workspace health", or "something seems wrong".
team-overview
Shows registered BotMinter teams, their members, roles, workspaces, and running state. Use when the operator asks to "show teams", "list teams", "who is on the team", "team status", "show members", or "what teams do I have". Reads ~/.botminter/config.yml and workspace directories.
profile-design
Designs and troubleshoots BotMinter profiles — team methodology templates that define roles, statuses, hats, skills, and process conventions. Use when the operator asks to "design a profile", "create a new role", "fork a profile", "fix my profile", "troubleshoot profile issues", "design a process workflow", "add a hat", "customize a profile", or "validate my profile". Operates on profile templates, not live team repos.
profile-browser
Browses and describes BotMinter profiles — team methodology templates that define roles, statuses, coding agents, and process conventions. Use when the operator asks to "list profiles", "show profiles", "what profiles are available", "describe a profile", "what roles does X have", or "compare profiles". Reads ~/.config/botminter/profiles/.