update-wiki
Syncs the local wiki directory with the GitHub repository wiki.
Install
mkdir -p .claude/skills/update-wiki && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12626" && unzip -o skill.zip -d .claude/skills/update-wiki && rm skill.zipInstalls to .claude/skills/update-wiki
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Publish the repo-root wiki/ specification tree to the HW-OpenClaw GitHub Wiki on demand. Use when the user asks to sync, publish, update, or refresh the GitHub Wiki from the version-controlled wiki/ directory.Key capabilities
- →Publish local `wiki/` content to GitHub Wiki
- →Clone GitHub Wiki into a temporary directory
- →Replace cloned content with local `wiki/` tree
- →Preserve directory structure and file names
- →Commit and push only when content changed
- →Remove temporary clone after publishing
How it works
The skill clones the GitHub Wiki, replaces its content with the local `wiki/` directory, commits and pushes changes if detected, and then cleans up the temporary clone.
Inputs & outputs
When to use update-wiki
- →Syncing wiki docs
- →Publishing spec changes
- →Updating project documentation
About this skill
Update Wiki
Use this skill to publish the version-controlled wiki/ tree to the GitHub Wiki.
The source of truth is always the repo-root wiki/ directory. The GitHub Wiki is only a generated mirror for web browsing.
Workflow
- Make sure the local branch contains the intended
wiki/content. - Run a dry run first:
python3 .codex/skills/update-wiki/scripts/update-wiki.py --dry-run --output /tmp/hw-openclaw-wiki-preview
- Inspect the generated preview if the change is non-trivial.
- Publish:
python3 .codex/skills/update-wiki/scripts/update-wiki.py
Behavior
- clones
https://github.com/<owner>/<repo>.wiki.gitinto a temporary local directory - replaces the clone content with the local
wiki/tree - preserves the
wiki/directory structure and file names as much as possible - copies Markdown pages and supported assets exactly as they live under
wiki/ - commits and pushes only when generated wiki content changed
- removes the temporary local wiki clone before the script exits
Authentication
The script uses normal Git commands.
If pushing fails, fix the local Git credential setup the same way you would for any other git push to GitHub.
Rules
- Do not edit the GitHub Wiki web UI as the source of truth.
- Do not publish unreviewed wiki changes.
- Do not keep the local wiki clone after publishing.
- If generated wiki output looks wrong, fix the versioned
wiki/source or the script, not the generated Wiki repo by hand.
When not to use it
- →When the GitHub Wiki is considered the source of truth
- →When unreviewed wiki changes are to be published
- →When the local `wiki/` directory is not the intended source
Limitations
- →Requires the local branch to contain the intended `wiki/` content
- →Does not support editing the GitHub Wiki web UI as the source of truth
- →Authentication relies on normal Git command setup
How it compares
This skill automates the synchronization of a local `wiki/` directory to a GitHub Wiki, ensuring the local version is the source of truth, unlike manual copy-pasting or direct GitHub Wiki edits.
Compared to similar skills
update-wiki side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| update-wiki (this skill) | 0 | 4mo | Review | Beginner |
| add-provider-doc | 6 | 3mo | Review | Beginner |
| update-release-notes | 1 | 29d | Review | Advanced |
| higress-daily-report | 1 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
add-provider-doc
lobehub
Guide for adding new AI provider documentation. Use when adding documentation for a new AI provider (like OpenAI, Anthropic, etc.), including usage docs, environment variables, Docker config, and image resources. Triggers on provider documentation tasks.
update-release-notes
tldraw
Update the release notes file at `apps/docs/content/releases/next.mdx` based on PRs merged to main since the previous release, or archive `next.mdx` to a versioned file when a new version is published.
higress-daily-report
alibaba
生成 Higress 项目每日报告,追踪 issue/PR 动态,沉淀问题处理经验,驱动社区问题闭环。用于生成日报、跟进 issue、记录解决方案。
sop-creator
coleam00
Create runbooks, playbooks, and technical documentation for engineering teams. Use when the user wants to document a process, create a runbook, build operational docs, or formalize any repeatable technical procedure. Triggers on requests like "create a runbook for...", "document this process", "write a playbook", or any technical documentation request.
release-prep
massgen
Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.
update-api-docs
Agenta-AI
Update the API reference documentation by downloading the latest OpenAPI spec from production and regenerating the Docusaurus API docs