Menu
Maintain the Velaclaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
Use the diffs tool to produce real, shareable diffs (viewer URL, file artifact, or both) instead of manual edit summaries.
Maintain an Obsidian-friendly memory wiki vault with wikilinks, frontmatter, and official Obsidian CLI awareness.
Tavily web search, content extraction, and research tools.
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
| name | wiki-maintainer |
| description | Maintain the Velaclaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates. |
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.velaclaw wiki ingest, velaclaw wiki compile, and velaclaw wiki lint as the default maintenance loop.bridge mode, run velaclaw wiki bridge import before relying on search results if you need the latest public memory artifacts pulled in.unsafe-local mode, use velaclaw wiki unsafe-local import only when the user explicitly opted into private local path access.obsidian.