Kb lint
A curated collection of WorkBuddy agent skills — academic pipeline, frontend slides, PPTX generator, tool-call repair, and more.
npx -y skills add yinqd3/workbuddy-skills --skill kb-lintAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Run comprehensive health checks on the Obsidian knowledge base including broken wikilinks, orphan pages, stale status, concept page completeness, and status consistency. Trigger phrases: lint knowledge base, knowledge base health check, kb check, run lint, 知识库检查, 健康检查.
SKILL.md
3.1 KB, as published. Nobody here has run it
Knowledge Base Lint (kb-lint)
Run health checks on an Obsidian knowledge base using the lint_kb.py script. Configure your vault path in the script or pass it as an argument.
When to Use
- User says "检查知识库", "跑一下 lint", "健康检查", "看看有没有断裂链接"
- After any significant ingest session (adding multiple new papers/projects)
- Before weekly or monthly maintenance
- When troubleshooting
[[wikilink]]issues
Available Script
<your-vault-path>/工具脚本/lint_kb.py — the comprehensive lint tool. Update VAULT_PATH in the script to point to your Obsidian vault.
Running Checks
⚠️ lint 报告仅输出到终端，不会写知识库文件。
Full check (all 5 categories)
cd "<your-vault-path>" && python "工具脚本/lint_kb.py"
Single category check
cd "<your-vault-path>" && python "工具脚本/lint_kb.py" --check broken-links
cd "<your-vault-path>" && python "工具脚本/lint_kb.py" --check orphans
cd "<your-vault-path>" && python "工具脚本/lint_kb.py" --check stale
cd "<your-vault-path>" && python "工具脚本/lint_kb.py" --check concept
cd "<your-vault-path>" && python "工具脚本/lint_kb.py" --check consistency
Verbose mode (show detailed progress)
cd "<your-vault-path>" && python "工具脚本/lint_kb.py" --verbose
Understanding Results
5 Check Categories
| Check | What it detects | Typical fixes |
|---|---|---|
| Broken wikilinks | [[目标]] pointing to non-existent files | Fix filename in link, or create missing card |
| Orphan pages | Pages with zero inbound [[wikilink]] | Add cross-references from related cards |
| Stale status | Cards with old status (e.g., "投稿中" unmodified >90 days) | Update status field in frontmatter |
| Concept completeness | Concept pages missing linked papers, or papers with matching tags not linked from concept page | Add related_papers to concept page frontmatter |
| Status consistency | Projects past end_date still "进行中", students past graduation without update | Update status or date in frontmatter |
Common Fix Patterns
-
Broken
[[wikilink]]: The target uses[[../子目录/文件]]relative paths. UseObsidian → Files & Links → Always update internal links: trueto auto-heal on rename. -
Stale status: Check the paper/project status against
日志.md— if status changed per log but frontmatter wasn't updated, correct it. -
Concept page missing refs: Add the paper's
[[wikilink]]to the concept page'srelated_papersfrontmatter list.
Maintenance Workflow
Weekly (recommended): Run full lint after each scan_vault.py weekly scan.
Post-ingest: Run lint after batch-adding 3+ new cards.
Monthly deep-clean: Run full lint and fix all issues.