dexio-wiki-captureCapture what an agent session settled into an LLM wiki before it is lost: at the end of a task or session (or over saved transcripts), pick out decisions, verified facts, corrections and working procedures, drop the chatter, and file each item on the page that owns it. Use when a session or task ends, before context is compacted, when a person says to remember something, or on a schedule over past agent sessions (Claude Code, Codex, Hermes, OpenClaw).
Install via ClawdBot CLI:
clawdbot install dexio/dexio-wiki-captureGenerated Oct 8, 2026
An engineering team uses Claude Code and Codex to build features daily, and each session leaves behind decisions, verified API behaviors, and working deployment procedures. At the end of every task, this skill extracts only durable items and files them on the correct wiki pages before the context window closes.
A solo consultant runs client calls with an AI assistant and needs every approved recommendation, constraint, and correction captured into a per-client wiki. The skill filters out unresolved plans and agent guesses, then records dated, sourced decisions so the next engagement starts from verified ground.
A research group relies on agent sessions to reconcile literature, verify numbers, and work out reproducible lab procedures. This skill captures proven procedures and corrections while dropping chatter, and flags unverified facts so they are never mistaken for confirmed results.
A support organization stores AI-assisted troubleshooting sessions as JSONL transcripts and needs recurring fixes filed as durable KB entries. Running the skill on a schedule over saved transcripts catches sessions that ended without capture, checks each item against the current wiki, and skips duplicates.
An Obsidian user wants their AI conversations to feed a personal wiki of decisions, preferences, and verified facts without turning it into a transcript dump. The skill keeps each capture to zero to five items, files them with dates and sources, and asks before recording anything ambiguous.
Distribute the skill freely under MIT to drive adoption across Claude Code, Codex, Hermes, and OpenClaw users. Community contributions expand compatibility and transcript parsers, while the author builds reputation as the standard for agent-session capture.
Bundle the skill as a capture layer inside an existing wiki or documentation platform (e.g., Obsidian sync, hosted wiki, enterprise KB). The platform supplies storage, sharing, and schema enforcement; the skill supplies structured, low-noise ingestion from agent sessions.
Offer a hosted service that ingests client transcripts on a schedule, applies the skill's capture steps, maintains state files, and reports filed items. Agencies and consultancies pay for reliable, auditable session-to-wiki pipelines without maintaining agents themselves.
💬 Integration Tip
Wire capture as an end-of-task hook or scheduler over saved transcripts, and pair it with the wiki-orient, wiki-record, wiki-conflicts, and wiki-shared skills so each item lands on the owning page with a dated source. Keep the state file at the wiki root (or agent workspace) and treat any multi-writer wiki as shared by searching immediately before each write.
Manage a personal knowledge base by adding, searching, organizing, and reviewing articles, links, and notes with tags and natural language queries.
Generate a daily work report by automatically discovering all git repositories the user worked on, collecting commit logs across all branches, and summarizin...
日记引导助手。每日写作引导、感恩日记、反思日记、晨间日记、晚间总结、周总结模板。Journal prompts for daily writing, gratitude, reflection, morning pages, evening review, weekly summary. 日记、写作、反思、感恩。
Use when maintaining RDR2 (Red Dead Redemption 2) playthrough notes — logging an acquisition ("acquired X", "got N gold bars", "finished X"), answering in-game location/crafting questions, or reviewing the notes for duplicate or stale info. Triggers on RDR2, Red Dead Redemption, playthrough, legendary animal, talisman, trinket, valerian root, gold bar, horse, weapon, berry.
Use when a sales rep already has a customer who has expressed some need (from outreach follow-up, account-landing research, customer-initiated contact, or meeting notes) and needs to structurally validate whether that need is real, urgent, whose pain it actually is, and whether it matches the team's capability — before pushing to ROI proofing or buying-intent assessment. Triggers: '验证一下这个需求是不是真的', '需求真不真', '客户说痛但我不确定', '这个客户值不值得跟', '客户说会考虑但是真的吗', '谁拍板', '现有方案是什么', '切换成本', 'need validation', 'pain point validation', 'is this a real need', 'verify customer need'. Do NOT use for: scoring leads at line-item level, building target-customer profiles, calculating ROI, overall buying-intent scoring, opportunity-stage assessment, or writing outreach/cold messages.
Microsoft OneNote integration. Manage Notebooks. Use when the user wants to interact with Microsoft OneNote data.