$ loading_
Maintain an OpenClaw memory wiki with deterministic, source-backed page updates.
The material indicates this is fundamentally an open-source prompt-only wiki maintenance skill with no declared secrets or remote endpoints, so overall risk is low. Caution is still warranted because the description involves reading, searching, and updating a local memory-wiki vault and may invoke local openclaw/Obsidian-related tooling depending on the runtime environment.
The material explicitly states that no keys or environment variables are required, and the README does not request any token, API key, or account authorization, so no clear credential leakage or abuse surface is shown.
No remote endpoints are declared, and the system flags it as prompt-only. Although the README mentions bridge/import flows that may pull public memory artifacts, the material does not specify any concrete data egress target or default network configuration.
The README explicitly references running commands such as `openclaw wiki ingest/compile/lint` and `bridge import`, indicating use in an environment that can invoke local tools/commands. This is a normal local execution capability for this type of skill, with no specific red flag showing privilege beyond the stated purpose.
The skill is intended to maintain a memory-wiki vault and references `wiki_get`, `wiki_apply`, `wiki_search`, and `wiki_lint`, which imply reading and updating local wiki/memory content. The README also mentions an `unsafe-local` mode for private local path access, but only with explicit user opt-in, so there is no evidence of default overbroad access.
The source is an open-source GitHub repository, the system flags it as open-source, and community adoption is very high (about 377k stars), all of which materially reduce risk. License and maintenance status are not clearly stated, leaving some governance uncertainty, but not enough on its own to raise this to high risk.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "wiki-maintainer" skill from askskill: 1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/extensions/memory-wiki/skills/wiki-maintainer/SKILL.md 2. Save it as ~/.claude/skills/wiki-maintainer/SKILL.md 3. Reload skills and tell me it's ready
Create a new 'Project Architecture' page in the OpenClaw memory wiki using a fixed template. Split it into Overview, Module Notes, Dependencies, and Sources. If related content already exists, merge it and preserve source links.
A consistently structured wiki page with managed sections, merged content, and traceable sources.
Update the 'API Change Log' page in the wiki based on this meeting note and design document. Only write information supported by explicit sources, mark added, changed, and removed blocks, and do not alter unrelated content.
An updated page with clearly scoped changes and source attribution for each modification.
Turn the following scattered notes into an OpenClaw wiki entry called 'Deployment Process'. Use a deterministic structure with prerequisites, steps, common issues, and references, and remove duplicated information.
A standardized deployment-process entry with fixed structure, deduplicated content, and references.
Use this skill when working inside a memory-wiki vault.
wiki_status first when you need to understand the vault mode, path, or Obsidian CLI availability.memory_search with corpus=all when the shared memory tools are available and you want one recall pass across durable memory plus the compiled wiki.wiki_search to discover candidate pages when you want wiki-specific ranking/provenance, then wiki_get to inspect the exact page before editing or citing it.wiki_apply for narrow synthesis filing and metadata updates when a tool-level mutation is enough.wiki_lint after meaningful wiki updates so contradictions, provenance gaps, and open questions get surfaced before you trust the vault.openclaw wiki ingest, openclaw wiki compile, and openclaw wiki lint as the default maintenance loop.bridge mode, run openclaw wiki bridge import before relying on search results if you need the latest public memory artifacts pulled in.unsafe-local mode, use openclaw wiki unsafe-local import only when the user explicitly opted into private local path access.obsidian.Verify an OpenClaw release is fully published and working across all channels.
Fetch GitHub issues, create fixes, open PRs, and handle reviews.
Convert text to speech locally and offline with sherpa-onnx, no cloud needed.
Regenerate OpenClaw release changelog sections from Git history before releases.
Prepare and verify OpenClaw stable or beta releases and release notes.
Create and review technical docs and agent instruction files in repositories.
Maintain an Obsidian-friendly knowledge vault with links, metadata, and structure.
Store durable memory in a GitHub-hosted Obsidian vault via markdown tools.
Inspect, patch, validate, and publish OpenClaw GHSA advisories securely.
Refactor OpenClaw docs pages with source-checked preservation, clearer structure, and verification.
Give Claude Code persistent cross-device memory with semantic recall and self-maintenance.
Store and retrieve persistent AI memories across sessions with contextual search.