wiki-update
Skill9 starsChanged 7 months agoMITView on GitHub
Targeted update to a single wiki page (not source-driven like /wiki-ingest). Use when you need to edit, correct, expand, or restructure a specific page based on user feedback or newly-discovered information. Reads the page and its Related links, drafts the change, presents the diff, and applies on approval.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
- chobizzy/llm-wikitheir own version, first seen Nov 1, 2026
- boaz-hwang/boaz-wikitheir own version, first seen Oct 25, 2026
- rumi-chan/llm-wikitheir own version, first seen Oct 25, 2026
- dagarre00/claude-code-templatetheir own version, first seen Oct 15, 2026
- 0xbadal/Skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use claude-history-ingest, graph-colorize and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Ivy-Chen1999Skillclaude-history-ingest
Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions their .claude folder, Claude projects, session data, past conversation logs, local-agent-mode sessions, or audit logs.
Also in 3 projects that use this
Ivy-Chen1999Skillgraph-colorize
Color-code the Obsidian graph view by rewriting `.obsidian/graph.json` colorGroups. Use this skill when the user says "color my graph", "color code obsidian", "colorize the graph", "color the graph by tag", "color by category", "highlight visibility in graph", "make the graph colorful", "distinguish tags in graph", or wants nodes in Obsidian's graph view tinted by tag, folder, or visibility. Generates a `colorGroups` array from the vault's actual tags/categories and merges it into the existing graph.json without clobbering other graph settings. Always backs up first.
Also in 3 projects that use this
nexuschainsSkillcross-linker
Scans the wiki vault and adds missing [[wikilinks]] between pages that are related but not yet connected. Use this skill when the operator says "link my pages", "find missing links", "cross-reference the wiki", "connect my wiki", "add wikilinks", or after any large ingest to weave new pages into the existing knowledge graph. Also trigger when orphaned pages need connecting or when wiki-lint reports fragmented tag clusters. This is a write-heavy skill — it modifies page files to insert links, unlike wiki-lint which only reports.
Also in 3 projects that use this
nexuschainsSkilltag-taxonomy
Enforces and normalizes tags across the wiki against the controlled vocabulary in wiki/schema/tag-taxonomy.md. Use this skill when the operator says "fix my tags", "normalize tags", "tag audit", "clean up tags", "tag taxonomy", or "my tags are a mess". Also use when creating or updating wiki pages and the right tags are unclear. Operates in three modes: Audit (report current state), Normalize (apply fixes), and Classify (tag a single new page). Always reads the taxonomy file before assigning any tags.
Also in 3 projects that use this
jehrhardtSkillwiki-capture
Quickly capture raw thoughts, links, images, or notes to today's Obsidian daily note from anywhere in Pi. Use when the user wants to jot something down for later wiki processing.
Also in 3 projects that use this
- +6 more from Ivy-Chen1999
- +1 more from nexuschains
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- Ar9av/obsidian-wiki★ 3.7ksame name
- kfchou/wiki-skills★ 189same name
- bozhouDev/bozhou-skills★ 78same name
- Ivy-Chen1999/llm-wiki-kit★ 21same name
- crabin/llm-wiki★ 8same name
- chobizzy/llm-wiki★ 3same name
- 0xbadal/Skills★ 1same name
- dagarre00/claude-code-template★ 1same name
- rumi-chan/llm-wiki★ 1same name
- boaz-hwang/boaz-wiki★ 0same 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 repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 12 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
If argument is a full path, use it directly.
- Distinctive: line 42
If the page doesn't exist, offer to:
- Distinctive: line 43
Create it as a stub (if user wants to start a new page)
- Distinctive: line 44
Check if it should be elsewhere (maybe user meant a different category)
- Very specific: line 55
Read every page referenced in the ## Related section.
- Very specific: line 71
If the page has an owner: other than wiki-curator, and the edit is domain-specific, delegate to the owner agent for a draft.
- Distinctive: line 77
Wait for the owner's draft.
- Very specific: line 79
If the edit is purely structural (formatting, cross-references, frontmatter), wiki-curator can handle it directly.
- Distinctive: line 93
Before presenting the change, verify:
- Very specific: line 97
No new broken [[wikilinks]] introduced
- Distinctive: line 102
If the edit adds or removes cross-references:
- Very specific: line 141
Update wiki/index.md if the page's status changed (stub → complete, etc.) or title changed
- Distinctive: line 155
After the update, run a quick sanity check on the affected pages:
- Distinctive: line 160
If any issues, report them and offer to fix in a follow-up update.
- Very specific: line 164
If the user requests updates to multiple pages (e.g., "add [[trove-cleanup]] to Related on all combat pages"), batch them:
- Distinctive: line 178
Read the raw source(s) that justified the upgrade
- Distinctive: line 179
Write the full content per the schema's required sections
- Distinctive: line 182
Run the standard diff/approval flow
“Common” is measured: kept by at least 6 in 10 of the 9 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
/wiki-update — Targeted Page Edit
Delegate to: wiki-curator (which may delegate to the page's owner)
Arguments
<page>— wiki page path (e.g.,wiki/services/DataStoreService.mdor justDataStoreService)[note]— optional reason or description of the change
When to Use
- User spotted an inaccuracy on a page
- Owner agent wants to refine their page without a new source
- Schema change requires touching multiple pages
- Contradiction resolution
- Adding missing cross-references
- Upgrading a stub to complete status
When NOT to Use
- Ingesting a new raw source → use
/wiki-ingestinstead - Fixing lint issues → use
/wiki-lint --fix - Creating a brand-new page for a topic from scratch with no source → write a proper page via
/wiki-ingestwith a raw source first
Workflow
1. Resolve the Page
If argument is a full path, use it directly. Otherwise, search for the page:
find wiki/ -name "*<arg>*.md" -not -path "wiki/raw/*"Handle ambiguity: if multiple matches, list them and ask user to disambiguate.
If the page doesn't exist, offer to:
- Create it as a stub (if user wants to start a new page)
- Check if it should be elsewhere (maybe user meant a different category)
2. Read the Page
Load the full page. Note:
owner:,status:,sources:,updated:from frontmatter- Current structure (which sections exist)
- Current
Relatedlinks
3. Read Related Pages
Read every page referenced in the ## Related section. Skim their content to understand the context.
Also load wiki/SCHEMA.md to ensure the edit complies with the schema.
4. Understand the Requested Change
Parse the user's intent:
- Correction — "this is wrong, fix it"
- Expansion — "add info about X"
- Restructure — "split this page" or "merge these sections"
- Cross-reference — "link to Y"
- Status upgrade — "this stub should be complete now"
- Schema conformance — "add missing required sections"
5. Delegate to Owner (If Appropriate)
If the page has an owner: other than wiki-curator, and the edit is domain-specific, delegate to the owner agent for a draft. Pass the owner:
- The current page content
- The requested change
- Any relevant Related page content
- The schema section for the page type
Wait for the owner's draft.
If the edit is purely structural (formatting, cross-references, frontmatter), wiki-curator can handle it directly.
6. Draft the Change
Produce the edit. Options:
In-place edit: For small changes, use Edit with old_string → new_string.
Section rewrite: For larger changes within a section, present the new section content.
Full page rewrite: For major restructures, present the full new page content.
7. Validate Against Schema
Before presenting the change, verify:
- Frontmatter still valid (all required fields present)
- H1 still matches
title: - Required sections still present (unless converting to stub)
- No new broken
[[wikilinks]]introduced updated:timestamp will be bumped to today
8. Update Related Links
If the edit adds or removes cross-references:
- For each added link: verify the target page exists (create stub if needed)
- For each added link: add reverse link in the target's Related section
- For each removed link: remove reverse link in the target's Related section
9. Present Diff to User
# Update Proposal: [[<Page Title>]]
**Reason:** <user's note>
**Owner:** <agent>
**Change size:** <small | medium | large>
**Schema check:** ✅ valid
## Diff
<show the before/after — for small edits, inline; for large, in a code fence>
## Side Effects
- Related page `[[X]]` will get a new back-link in its Related section
- Frontmatter `updated:` will change from 2026-03-10 → 2026-04-16
- `sources:` will <be unchanged | gain a new citation>
## Approval needed
Proceed?10. Wait for Approval
On approval, apply the change and any side effects.
11. Apply the Update
- Edit the target page
- Bump
updated:in frontmatter to today - Apply Related link side effects on other pages
- Update
wiki/index.mdif the page'sstatuschanged (stub → complete, etc.) or title changed
12. Append to Log
## [YYYY-MM-DD] update | [[<Page Title>]]
- Reason: <note>
- Change: <one-line summary>
- Status: <old status> → <new status> (if changed)
- Side effects: <pages with added/removed back-links>13. Run a Mini-Lint
After the update, run a quick sanity check on the affected pages:
- Frontmatter still valid
- Required sections still present
- All wikilinks resolve
If any issues, report them and offer to fix in a follow-up update.
Batch Updates
If the user requests updates to multiple pages (e.g., "add [[trove-cleanup]] to Related on all combat pages"), batch them:
- Collect all target pages
- Draft changes for each (in parallel if simple, delegated if complex)
- Present combined diff
- One approval, one application pass
- One log entry per page, or one grouped entry if the changes are uniform
Stub → Complete Upgrade Pattern
A common update: converting a stub page to a complete page, usually after a new source was ingested.
Workflow:
- Read the stub
- Read the raw source(s) that justified the upgrade
- Write the full content per the schema's required sections
- Change
status: stub→status: complete - Add
sources:citations - Run the standard diff/approval flow
Anti-Patterns
- ❌ Do not edit a page without reading it fully first
- ❌ Do not break wikilinks (either resolve new links to real pages or create stubs)
- ❌ Do not skip the Related link side-effects (bidirectional links must stay consistent)
- ❌ Do not forget to bump
updated: - ❌ Do not merge domain-specific edits without delegating to the owner
- ❌ Do not silently resolve contradictions — those require explicit approval
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.

