verify

Validate knowledge base structure, links, and abstract fidelity.

226|55|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Miosa-osa/canopy --skill verify-miosa-osa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/Miosa-osa/canopy/tree/main/library/skills/processing/verify
Command: npx skills add https://github.com/Miosa-osa/canopy --skill verify-miosa-osa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and fix quality issues in knowledge base content by validating structure, required fields, and link integrity, while ensuring abstracts stay aligned with full content. It runs as a non-blocking gate and reports warnings to prevent workflow disruption.

Core Features & Use Cases

  • Structural checks: YAML frontmatter presence; parseable; required fields exist (type, title, date); Markdown structure validity; file naming conventions.
  • Schema checks: Validate that related files (e.g., context.md, signal.md, claims) meet required schema fields (e.g., context sections, date, priority, status, tags, etc.).
  • Link checks: Validate internal references exist; anchors exist; avoid circular references beyond depth 3.
  • Fidelity checks: Read L0 abstracts and full content; compute semantic alignment; flag drift when alignment falls below a threshold (e.g., 0.7).
  • Duplicate detection: Detect high-content overlap across files and flag for deduplication.

Quick Start

Run the /verify command across your knowledge base to initiate quality validation.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I validate YAML frontmatter and required fields in my knowledge base?

Knowledge base validation parses YAML frontmatter to ensure required fields like type, title, and date exist, checks Markdown structure, and verifies file naming conventions to prevent content quality issues.

Can I check internal links and anchors for broken references in a knowledge base?

Internal link checks validate that referenced files and anchors exist within the knowledge base, while also detecting and flagging circular references beyond a depth of three to maintain content integrity.

What is the best way to detect content drift between abstracts and full articles?

Fidelity checks read L0 abstracts and full content to compute semantic alignment, automatically flagging drift when alignment falls below a 0.7 threshold to catch content misalignment.

How do I find duplicate content across markdown files?

Duplicate detection scans the knowledge base to identify high content overlap across files, flagging them for deduplication to consolidate redundant entries and maintain a single source of truth.

Does schema validation support custom context and signal file structures?

Schema validation checks that related files like context.md and signal.md meet required schema fields, verifying context sections, date, priority, status, and tags to ensure structural compliance.

Will knowledge base validation block my workflow if it finds issues?

No, verification runs as a non-blocking gate that reports warnings for structural, schema, and link issues, allowing you to catch and fix problems without disrupting your workflow.