knowledge
Skill0 starsChanged 8 months agoMITView on GitHub
Knowledge base update from field data. Scans the week's operational data for new patterns, structures them, and writes to department knowledge bases. Thursday-Friday routine. Octopus colors: Yellow (pattern extraction) + Red-Orange (structure) + Blue (implementation).
13 other projects use a version of this.
Adopted by
Most recently taken up by
- guaardvark/guaardvarktheir own version, first seen Nov 13, 2026
- overment/skillstheir own version, first seen Nov 8, 2026
- vzhukovs/podman-desktop-kittheir own version, first seen Nov 1, 2026
- rubixkube-io/rubixkube-for-aitheir own version, first seen Oct 20, 2026
- lablup/backend.aitheir own version, first seen Oct 8, 2026
- youdcode/open-companytheir own version, first seen Sep 21, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- lablup/backend.ai★ 681same name
- guaardvark/guaardvark★ 320same name
- Kastalien-Research/thoughtbox★ 64same name
- overment/skills★ 31same name
- SonyHarv/claude-polyrouter★ 2same name
- youdcode/open-company★ 2same name
- Ahmadjamil888/imos★ 1same name
- njt2810/claude-code-framework★ 1same name
- rubixkube-io/rubixkube-for-ai★ 1same name
- Ekajto/my-claude-skills★ 0same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read .chairman/config.json for active departments
- Distinctive: line 23
Check for contradictions with existing knowledge base entries
- Very specific: line 26
Write new entries to departments/{dept}/knowledge/
- Distinctive: line 27
Update existing entries if information has changed
- Very specific: line 28
Remove outdated entries (move to _archive/ subfolder)
- Very specific: line 53
Never delete knowledge base entries.
- Very specific: line 54
Check for contradictions before writing.
- Distinctive: line 55
Do not add speculative knowledge.
- Distinctive: line 56
If $ARGUMENTS targets a specific department, only update that one.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/knowledge: Knowledge Base Update
Octopus Colors: Yellow (Researcher) + Red-Orange (Designer) + Blue (Maker)
Process
- Read
.chairman/config.jsonfor active departments - For each department (or specific department if $ARGUMENTS provided):
- Scan for new knowledge (Yellow):
- Recent reports in
.chairman/reports/ - Recent assignments and their outputs
- Patterns: recurring issues, common objections, process gaps
- Customer feedback or market signals
- Recent reports in
- Structure the knowledge (Red-Orange):
- Categorize: process update, FAQ, pattern, correction
- Check for contradictions with existing knowledge base entries
- Format consistently with existing entries
- Implement updates (Blue):
- Write new entries to
departments/{dept}/knowledge/ - Update existing entries if information has changed
- Remove outdated entries (move to
_archive/subfolder)
- Write new entries to
Output Format
# Knowledge Base Update: [Date]
## Updates Made
### [Department]
- **Added:** [filename] - [what was added and why]
- **Updated:** [filename] - [what changed]
- **Archived:** [filename] - [why it is outdated]
### [Department]
...
## Summary
- Total updates: [count] across [dept count] departments
- New entries: [count]
- Updated: [count]
- Archived: [count]Rules
- Never delete knowledge base entries. Archive them to
_archive/. - Check for contradictions before writing. If found, flag to Chairman.
- Do not add speculative knowledge. Only patterns supported by data.
- If $ARGUMENTS targets a specific department, only update that one.
- Notify Chairman of significant additions (new process, corrected procedure).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

