Install
$ agentstack add skill-kfchou-wiki-skills-wiki-update ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Wiki Update
Revise existing wiki pages. Always show diffs before writing. Always log. Always cite the source of new information.
Pre-condition
Find SCHEMA.md (search from cwd upward, or ~/wikis/). If not found, tell the user to run wiki-init first. Read it to get wiki root path and conventions.
Process
1. Identify what to update
The user may provide:
- Specific page names — update those pages
- New information — read
wiki/index.mdto find affected pages, then read those pages - A lint report — work through its recommendations item by item
2. For each page to update
Read the current content in full. Propose the change:
> Current: ` > **Proposed:** > **Reason:** > **Source:** `
Always include Source. An edit without a source citation creates untraceability — future you won't know why the change was made.
Ask for confirmation before writing each page. Do not batch-apply changes without per-page confirmation.
3. Check for downstream effects
After identifying the primary pages to update, grep for [[slug]] references to those pages across all of wiki/pages/. For each page that links to an updated page:
- Does the update change anything that page asserts?
- If yes: flag it explicitly — "[[other-page]] may also need updating based on this change"
- Offer to update it with the same confirm-before-write flow
4. Contradiction sweep
If the new information contradicts something in the wiki: search all pages for the contradicted claim before updating. It may appear in more than one place. Update all occurrences, not just the most obvious one.
5. Update wiki/index.md
If the one-line summary for any updated page has changed, update it in index.md. Update the updated date in the page's frontmatter.
6. Update wiki/overview.md
Re-read overview.md. If the updates shift the overall synthesis (new understanding, resolved open question, changed key claim), propose edits to overview.md using the same confirm-before-write flow.
7. Append to wiki/log.md
Always append — do not ask permission, do not skip if log.md exists:
## [] update |
Reason:
Source:
Common Mistakes
- Updating without citing the source — Always include where the new information came from. This makes the wiki auditable.
- Skipping the downstream check — An update that contradicts a page's content while leaving pages that link to it unchanged creates silent inconsistency.
- Skipping the log — Every change must be logged. The log is append-only; if
log.mddoesn't exist, create it. - Batch-writing without confirmation — Show each diff individually. The user may accept some changes and reject others.
- Appending instead of updating — Do not add
## [date] updatesections to page bodies. Edit the relevant section in-place, bump theupdatedfrontmatter date, and log the change inlog.md. If you find existing date-stamped sections, offer to integrate them in-place as part of the update.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: kfchou
- Source: kfchou/wiki-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.