thought-forest-kb-audit

Scan Thought Forest notes for metadata drift and quality issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BakerSean168/thought-forest --skill thought-forest-kb-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thought-forest-kb-audit
Source: https://github.com/BakerSean168/thought-forest/tree/main/config/skills/thought-forest-kb-audit
Command: npx skills add https://github.com/BakerSean168/thought-forest --skill thought-forest-kb-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Use this Skill to scan the Thought Forest repository for note quality issues, metadata gaps, tag drift, placeholder content, duplicate risks, or stale prompt files before planning a cleanup batch.

Core Features & Use Cases

  • Detect missing frontmatter fields, blank or placeholder descriptions, and missing type/* or status/* tags across notes.
  • Identify duplicate titles or aliases and missing related notes blocks to improve navigation and consistency.
  • Propose scoped cleanup batches and provide guidance on using related skills like thought-forest-note-intake and thought-forest-note-refactor to perform isolated fixes.

Quick Start

Run the audit script from the repository root to surface findings and guidance.

Frequently Asked Questions about thought-forest-kb-audit

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

FAQPage Schema
How do I audit a knowledge base for missing frontmatter and tag drift?

To audit a knowledge base for missing frontmatter and tag drift, you can run a repository-wide scan that surfaces metadata gaps, placeholder content, and missing type/status tags. This generates findings to guide scoped cleanup tasks.

What is the best way to find duplicate titles and placeholder content in my notes?

Finding duplicate titles and placeholder content in notes requires scanning the vault to identify blank descriptions, duplicate aliases, and missing related notes blocks. This process highlights navigation gaps and consistency issues for batch remediation.

How do I check for stale agent rules and missing metadata in a documentation repository?

Checking for stale agent rules and missing metadata in a documentation repository involves scanning all notes to validate frontmatter completeness and detect outdated prompt files. The output provides guidance for performing isolated fixes using related refactoring skills.

Can I batch cleanup tasks for notes with missing related links and status tags?

Yes, you can batch cleanup tasks for notes with missing related links and status tags by running an audit script from the repository root. The audit proposes scoped cleanup batches designed to guide targeted remediation across the affected notes.

Does this note quality audit work with existing note intake and refactor workflows?

Yes, the note quality audit integrates with existing note intake and refactor workflows by providing guidance on using related skills to perform isolated fixes. It surfaces the exact metadata issues needed to scope remediation actions effectively.