validate

Validates notes against domain-specific templates for schema compliance.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/lightningfastsls/London_Lab --skill validate-lightningfastsls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/lightningfastsls/London_Lab/tree/main/.claude/skills/validate
Command: npx skills add https://github.com/lightningfastsls/London_Lab --skill validate-lightningfastsls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Notes often lack consistent structure and metadata, making downstream processing and audits unreliable. This skill enforces domain-specific templates and validates key fields, enums, and link health to improve note reliability. It operates non-blockingly, warning on issues during capture.

Core Features & Use Cases

  • Validates required fields, enums, and description quality against domain templates.
  • Checks link health to ensure references remain accessible.
  • Non-blocking — warns during capture without blocking note ingestion for later correction.

Quick Start

Run the validator on a note to verify its schema compliance.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I validate notes against a schema without blocking the capture workflow?

You can use non-blocking note validation to warn about schema compliance issues during capture without halting note ingestion. This approach enforces domain templates, checks required fields, and flags issues for later correction.

What is domain template validation for structured notes?

Domain template validation is the process of checking captured notes against specific schemas to ensure required fields, enums, and description quality meet expected standards. It improves note reliability for downstream processing and audits.

Can I check link health and required fields in my notes during capture?

Yes, you can check link health to ensure references remain accessible and validate required fields simultaneously. The validator verifies schema compliance and warns you of issues non-blockingly as notes are captured.

What's the best way to enforce consistent metadata and structure across captured notes?

The best way to enforce consistent metadata is to validate notes against domain-specific templates. This ensures schema compliance by checking required fields, enums, and description quality while operating non-blockingly to warn on issues.

Why does non-blocking validation warn instead of rejecting notes with schema issues?

Non-blocking validation warns instead of rejecting to ensure note capture is never blocked during ingestion. This allows users to capture notes immediately while flagging template compliance issues, broken links, and missing fields for later correction.