kb-curate

Audit a knowledge base for wikilink, tag, taxonomy, and verification hygiene defects.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill kb-curate-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-curate
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/kb-curate
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill kb-curate-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Knowledge bases accumulate structural rot over time: broken wikilinks, hardcoded user paths, tag drift, stale verification stamps, and broken supersede chains. This Skill audits an entire vault for these hygiene issues and optionally applies the two mechanically safe fixes, so you can keep a vault trustworthy without manually inspecting every note. ## Core Features & Use Cases - Vault-wide hygiene audit: Detects 16 rule violations across six categories including unresolved wikilinks, basename collisions, hardcoded /Users/ paths, tag aliases, taxonomy drift, stale verification, and supersede-chain defects, each with a severity level. - Conservative auto-remediation: With --apply, performs only the two mechanically safe fixes: tag canonicalization (delegated to kb-edit) and path-only wikilink rewrites that preserve aliases, anchors, and link style. Everything else stays report-only with a named follow-up command. - Structured JSON output: Returns findings partitioned by severity, a summary, and per-fix results, with categorical error codes like invalid-config, no-kb-resolvable, and readonly-kb. - Use Case: Run a read-only report on your coding knowledge base with a 30-day staleness threshold, review the findings, then apply the safe fixes and manually handle the report-only items using the named kb-edit follow-up commands. ## Quick Start Ask the agent to audit the coding knowledge base for hygiene issues and apply the safe fixes.

Frequently Asked Questions about kb-curate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a knowledge base for broken wikilinks?

Run the kb-curate helper in read-only mode against your vault, for example with --kb coding. It reports unresolved wikilinks, basename collisions, and cross-store link errors as structured JSON findings with severity levels, without modifying any notes.

What fixes does a knowledge base hygiene audit apply automatically?

With --apply, only two mechanically safe fixes run: tag canonicalization through kb-edit's alias map, and rewriting path-qualified wikilinks whose basename resolves to exactly one note. All other findings stay report-only and name the follow-up command to run.

Can I run the audit against a read-only knowledge base?

Yes, a read-only report run accepts a KB marked readonly: true in kb.yaml. However, using --apply against a readonly KB is refused with the readonly-kb error code, so drop --apply or use a writable KB.

Why does the audit fail with an invalid-config error?

The invalid-config error means a .kb/config.yaml, tag-aliases.yaml, or taxonomy.yaml file in the store is malformed. The error message names the offending file; fix its YAML syntax and rerun the audit.

How is verification staleness detected in notes?

Notes with a last-verified frontmatter field older than the --stale-after threshold (default 90 days) are flagged as verification.stale. Notes without the field are only flagged when the vault has adopted verification elsewhere, and malformed values never count as adoption.