richfrem/obsidian-wiki-linter
plugins/obsidian-wiki-engine/skills/obsidian-wiki-linter/SKILL.md
Runs a semantic health check over the Obsidian LLM wiki using the cheapest available LLM CLI. Finds inconsistencies, missing concepts, stale articles, connection candidates, and new article suggestions. Writes a structured report to meta/lint-report.md. Use when the wiki is large enough to have quality drift, or as a periodic maintenance step.
$ install --global
skillsauthnpx skillsauth add richfrem/agent-plugins-skills obsidian-wiki-linterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 7:40 AM53.2s6 files scanned
SKILL.md
- name:
- obsidian-wiki-linter
- plugin:
- obsidian-wiki-engine
- description:
- Runs a semantic health check over the Obsidian LLM wiki using the cheapest available LLM CLI. Finds inconsistencies, missing concepts, stale articles, connection candidates, and new article suggestions. Writes a structured report to meta/lint-report.md. Use when the wiki is large enough to have quality drift, or as a periodic maintenance step.
- allowed-tools:
- Bash, Read, Write
Dependencies
Requires Python 3.8+ and at least one CLI installed: copilot, claude, or gemini.
pip install -r requirements.txt
Obsidian Wiki Linter
Status: Active Author: Richard Fremmerlid Domain: Obsidian Wiki Engine
Purpose
Performs a semantic health check over the LLM wiki — the step Karpathy calls
"linting." Unlike audit.py (which checks structural coverage: orphans, missing
summaries, broken wikilinks), this skill uses an LLM to analyze semantic quality:
contradictions, knowledge gaps, and connection opportunities that only emerge once
the wiki is large enough to have internal consistency requirements.
What It Checks
| Category | What it finds | |:---------|:--------------| | Inconsistencies | Contradicting claims between two concept pages | | Missing Concepts | Topics implied by existing articles but not yet written | | Stale Articles | Pages with vague, outdated, or thin content | | Connection Candidates | Concept pairs that should have wikilinks but don't | | New Article Suggestions | Topics the wiki should cover based on its current scope |
Usage
Run semantic health check (default engine)
python ./scripts/lint_wiki.py --wiki-root /path/to/wiki-root
Sample more pages for larger wikis
python ./scripts/lint_wiki.py --wiki-root /path/to/wiki-root --sample 30
Force engine
python ./scripts/lint_wiki.py --wiki-root /path/to/wiki-root --engine claude
Dry run (print prompt without calling LLM)
python ./scripts/lint_wiki.py --wiki-root /path/to/wiki-root --dry-run
Engine Fallback Chain
Same strict cheap-model chain as obsidian-rlm-distiller:
1. copilot → gpt-5-mini (free with Copilot Pro)
2. claude → claude-haiku-4-5 (fallback)
3. gemini → gemini-3-flash-preview (final fallback)
Output
Report is written to {wiki-root}/meta/lint-report.md with YAML frontmatter:
generated_at: "2026-04-16T..."
engine: "claude"
model: "claude-haiku-4-5"
Followed by five sections:
- Inconsistencies — conflicting claims between articles
- Missing Concepts — implied but not yet written
- Stale or Weak Articles — need richer content
- Connection Candidates — wikilinks to add
- New Article Suggestions — fresh topics to write
When to Use
- After the wiki reaches ~20+ concept nodes (semantic quality starts to matter)
- As a weekly maintenance step before a major query session
- When you notice the wiki feels inconsistent or fragmented
- Before filing
--save-asoutputs back — lint first to know what gaps to fill - As the final step in
/wiki-rebuild(after ingest, distill, build)
Audit vs. Lint
| audit.py | lint_wiki.py |
|:-----------|:---------------|
| Structural: missing summaries, broken links, orphans | Semantic: contradictions, gaps, stale content |
| Always fast, no LLM needed | Requires LLM call |
| Run before every /wiki-query | Run periodically (weekly or post-rebuild) |
| Exit code 1 on critical issues | Always exits 0 (report-only) |
Related Scripts
lint_wiki.py— semantic health check orchestratoraudit.py— structural coverage checker (complementary)distill_wiki.py— shares engine detection logic
Related Skills
richfrem/vector-db-ingest
tools
VerifiedTrustedCommunity
Ingests repository files into the ChromaDB vector store. Builds or updates the vector index from a manifest or directory scan using ingest.py. Use when new files need to be indexed or the vector store is out of date. <example> user: "Index these new plugin files into the vector database" assistant: "I'll use vector-db-ingest to add them to the vector store." </example> <example> user: "The vector store is missing recent files -- update it" assistant: "I'll use vector-db-ingest to re-index the changes." </example>
3SKILL.mdUpdated Jun 2, 2026
richfrem/vector-db-cleanup
data-ai
VerifiedTrustedCommunity
Removes stale and orphaned chunks from the ChromaDB vector store for files that have been deleted or renamed. Use after files are removed or moved to keep the vector index in sync with the filesystem. <example> user: "Clean up the vector store after I deleted some files" assistant: "I'll use vector-db-cleanup to remove orphaned chunks." </example> <example> user: "The vector database has chunks for files that no longer exist" assistant: "I'll run vector-db-cleanup to prune them." </example>
3SKILL.mdUpdated Jun 2, 2026
richfrem/vector-db-audit
testing
VerifiedTrustedCommunity
Audit Vector DB coverage -- compares the live filesystem manifest against the ChromaDB index to identify coverage gaps.
3SKILL.mdUpdated Jun 2, 2026
richfrem/rlm-search
development
VerifiedTrustedCommunity
3-Phase Knowledge Search strategy for the RLM Factory ecosystem. Auto-invoked when tasks involve finding code, documentation, or architecture context in the repository. Enforces the optimal search order: RLM Summary Scan (O(1)) -> Vector DB Semantic Search -> Grep/Exact Match. Never skip phases.
3SKILL.mdUpdated Jun 2, 2026