dexio-wiki-setupStart a new LLM wiki or bring an existing folder of notes or Obsidian vault under maintenance: write the SCHEMA page that tells every agent the wiki's domain, folder layout, page types, frontmatter, tags and thresholds, and point each agent's instructions file at it. Use when creating a knowledge base that agents will maintain, when a wiki has no schema page, or when agents keep writing pages in inconsistent shapes.
Install via ClawdBot CLI:
clawdbot install dexio/dexio-wiki-setupGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 7, 2026
A consultant wants a durable home for concepts, entities, and decisions gathered while reading papers, vendor docs, and customer calls. They set up a git-backed folder, write SCHEMA.md from the template, and point their AI agent at it so every captured note lands in a consistent shape. Over time the wiki becomes a searchable second brain rather than a pile of unlinked markdown.
A platform team needs decisions, procedures, and incident learnings written down in one place by both engineers and their coding agents. They define page types for decisions and procedures, mandatory frontmatter with descriptions, and a short approved tag list, then add the wiki pointer block to AGENTS.md. Review digests and escalations are routed to the named owners from the schema.
A writer has hundreds of loosely organized Obsidian notes with inconsistent tags and missing frontmatter. They run wiki-lint to survey pages and broken links, commit the vault to git, then write a schema that reflects the best existing structure instead of an ideal one. Frontmatter and descriptions are added in batches starting from the most linked pages.
A company running several AI agents across machines wants one shared wiki with a hosted MCP server so agents and humans see the same pages. The schema defines folders by subject, trust labels for vendor claims versus estimates, and thresholds for when a subject earns its own page. Agents read the schema before substantial work and record durable findings on the correct page.
A lab needs a place where students and their agents record methods, results, and decisions without leaking credentials or raw chat. The schema names the domain boundaries explicitly (not a transcript store, not the system of record for live data) and lists what never goes in. Real pages are seeded from existing sources rather than empty placeholders.
The wiki operates as internal tooling that reduces duplicated research and inconsistent documentation across teams. Value shows up as faster onboarding, fewer repeated questions, and agent outputs that stay aligned with the schema. Cost is mostly setup time plus periodic schema maintenance.
Independent consultants or agencies charge to stand up wikis for clients, migrate existing Obsidian vaults, and write schemas tailored to each domain. Follow-on work includes lint passes, refactors, and agent instruction integration.
A hosted wiki with an MCP server is sold as a shared memory layer that any agent or teammate can query. The schema becomes the contract that keeps many writers producing consistent pages. Pricing scales with seats, agents, or storage.
💬 Integration Tip
Start with one git-backed folder, copy SCHEMA.template.md, and add the wiki pointer block to AGENTS.md or CLAUDE.md before seeding a handful of real pages—skip empty placeholders and hand-kept indexes until scale forces them.
Scored Oct 7, 2026
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.