local-wiki
Skill2 starsChanged 3 months agoMITView on GitHub
Ingest source content (ClickUp cards, meeting notes, transcripts, specs) into the project's governed local knowledge base. Dynamically locates the wiki (prefers docs/wiki/), then obeys the wiki's own AGENTS.md for structure and rules. Trigger: 'ingest into the wiki', 'add to wiki', 'capture this card/note locally', or any workflow that needs to persist a source doc locally before working on it.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- garbageek/claude-pluginstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- garbageek/claude-plugins★ 1same name
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.
In this repository53 other files it gives its agents.
- instructions/AGENTS.mdAGENTS.md
- skills/software-development/php-best-practices/AGENTS.mdAGENTS.md
- instructions/CLAUDE.mdCLAUDE.md
- architecture-designerSkill
- caveman-commitSkill
- caveman-compressSkill
- cavemanSkill
- conventional-commitSkill
- youtube-contentSkill
- agentkit-skill-authoringSkill
- skill-orchestrationSkill
- analogical-thinkingSkill
- investigateSkill
- ponytailSkill
- systematic-debuggingSkill
- mermaid-diagramsSkill
- feature-forgeSkill
- find-skillsSkill
- impeccableSkill
- javascript-proSkill
- legacy-modernizerSkill
- migrationSkill
- no-ai-slopSkill
- olakunlevpn-filament-skillsSkill
- clickupSkill
- clickup-tweak-workflowSkill
- git-advancedSkill
- mr-reviewSkill
- php-proSkill
- doxSkill
- improveSkill
- openspecSkill
- scrutinizeSkill
- systems-thinkingSkill
- tweakSkill
- tweak-workflowSkill
- prompt-engineerSkill
- laravel-best-practicesSkill
- pest-testingSkill
- php-best-practicesSkill
- security-audit-lightSkill
- security-best-practicesSkill
- spatie-javascriptSkill
- spatie-laravel-phpSkill
- spatie-securitySkill
- spatie-version-controlSkill
- tailwindcss-developmentSkill
- test-driven-developmentSkill
- sql-proSkill
- typescript-proSkill
- ui-ux-pro-maxSkill
- vue-expert-jsSkill
- vue-expertSkill
The file
Files
Local Wiki
Ingest source content into the project's governed local wiki — the append-only raw corpus + rebuild-only topic pages that capture knowledge before it scrolls away in ClickUp/chat. This skill locates the wiki dynamically and defers to its own governance for the exact structure; it does not hardcode one layout.
Locate the wiki (dynamic — prefer docs/wiki/)
A wiki is "governed" if it has an AGENTS.md (or CLAUDE.md) defining its
layout. Search in this order, use the first match, prefer docs/wiki/:
for d in docs/wiki wiki docs/kb docs/knowledge docs/notes; do
if [ -f "$d/AGENTS.md" ] || [ -f "$d/CLAUDE.md" ]; then echo "WIKI=$d"; break; fi
done- Found → set
WIKI=<dir>, read<WIKI>/AGENTS.mdand obey it (DOX: nearest AGENTS.md wins). - Ambiguous (several candidates, none
docs/wiki/) → list them and ask the user. - None found → ask the user where the wiki lives, or whether to bootstrap a minimal
docs/wiki/. Do not silently invent a structure.
Obey the wiki's own governance
The wiki's AGENTS.md is the source of truth for: the raw-corpus layout, page
format, what's append-only vs rebuild-only, whether the tree is git-ignored, and
URL-sourcing rules. Read it before writing. Never hand-edit rebuild-only
pages; never delete from the append-only raw corpus.
Ingestion pattern (adapt to the wiki's actual structure)
- Fetch the source via the right skill —
clickupfor a ClickUp card (show_task.py <ID>+show_comments.py <ID>). For meeting notes / transcripts / specs, take the user-provided content. - Write to the append-only raw corpus at the wiki-defined path, with the
wiki-required front-matter. For the standard
docs/wikilayout:- ClickUp card →
<WIKI>/raw/clickup/<ID>-<slug>.mdwithcustom_id:andurl:copied from the card (never retype a URL). - Other sources → the subdir the wiki's AGENTS.md specifies.
- ClickUp card →
- Rebuild the topic page per the wiki's rebuild flow — for
docs/wiki:pages/<slug>.mdin the canonical meta-block format, then updateindex.mdand append a one-linelog.mdentry. - Don't touch a consumer-facing changelog (e.g.
docs/wiki/CURRENT-CHANGELOG.md) from ingestion — it has its own separate, human-reviewed workflow.
Reference implementation (docs/wiki)
The convention this skill defaults to when the wiki's AGENTS.md is silent:
| Path | Role | Rule |
raw/clickup/ | one file per GYMED-XXX ClickUp task | append-only |
raw/ (other) | meeting notes, transcripts, exports | append-only |
pages/ | one topic page per source, AI-built | rebuild-only — never hand-edit |
glossary/ | domain terms | rebuild-only |
queries/ | saved query outputs | add; rewrite only if stale |
index.md | catalog | update on every page change |
log.md | wiki changelog | append-only |
CURRENT-CHANGELOG.md | consumer release notes | separate workflow — don't touch on ingest |
Pitfalls
- Nearest AGENTS.md wins — if
<WIKI>/AGENTS.mdcontradicts this skill, follow the wiki, not this file. - Pages are rebuild-only — to change a page, rebuild it from
raw/; don't hand-edit. raw/is append-only — never delete or overwrite an existing export.- URLs are copied, never retyped — paste from the source front-matter/body.
- Often git-ignored / local-only — the whole tree commonly stays on contributor machines; don't assume it's committed.
- Don't auto-create a wiki — if none is found, ask; bootstrapping a governed wiki is a decision, not a side effect.
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.

