dexio-wiki-lintCheck an LLM wiki's health and fix what it finds: broken links, leaked credentials, orphaned and unreferenced pages, missing frontmatter or descriptions, stale pages, oversized pages and duplicate titles. Ships a zero-dependency Python checker for markdown folders ([[wikilinks]] and relative links, Obsidian-compatible). Use on a schedule, before committing or merging wiki changes, after a refactor, or when an agent reports it cannot find a page.
Install via ClawdBot CLI:
clawdbot install dexio/dexio-wiki-lintGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://clawhub.ai/user/dexioAudited Oct 4, 2026 · audit v1.0
Generated Oct 4, 2026
A platform team runs the linter as a CI step on every pull request touching their markdown knowledge base. Broken links and credential-shaped strings fail the build before merge, while orphans, stale pages, and long pages are posted as review comments for a human to judge.
A company running autonomous coding and support agents schedules a weekly lint pass over the wiki those agents read. The agent fixes link and frontmatter defects automatically and escalates structural findings like duplicates and oversized pages to a human owner.
A research consultancy maintains client-facing and internal notes in an Obsidian vault spanning years of projects. They run the checker before archiving a project, repair renamed-page links, add missing descriptions, and use --catalog to regenerate the vault index instead of hand-maintaining index.md.
A security engineer uses the secret detection to scan an engineering wiki and runbooks for accidentally pasted API keys and tokens. Findings trigger immediate removal, notification of the credential owner, and rotation, with the checker's value-redaction report as evidence.
A docs team plans a large rename of product concepts and must update every incoming link. They run --links-to on the affected paths first to enumerate impacted pages, perform the rename, then re-lint until zero broken links remain.
The linter script is free and MIT-licensed, driving adoption among Obsidian and git-wiki users. Revenue comes from a hosted wiki platform (Dexio) that offers the same checks over MCP as wiki_health plus sync, search, and multi-agent collaboration.
A vendor packages the checker with pipeline integrations, dashboards, and policy controls for engineering organizations that want documentation gates. Teams pay per repository or per pipeline run for reporting, alerting, and historical trend data.
An agency or tooling provider runs scheduled lint-and-fix agent runs for clients, handling judgment calls like merging duplicates and rewriting stale pages. Clients get periodic reports and a maintained catalog without dedicating internal staff.
💬 Integration Tip
Drop scripts/wiki_lint.py into CI or a pre-commit hook with no dependencies to fail on broken links and secrets immediately, and use the --json or --catalog output to feed agent workflows or regenerate indexes automatically.
Scored Oct 4, 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.