From distill
Classify a single URL as insight or noise, and add it to the vault if applicable
How this command is triggered — by the user, by Claude, or both
Slash command
/distill:check <url>Files this command reads when invoked
This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
## Context Read the skill definition for output formats and classification criteria: - @skills/distill/SKILL.md - @skills/distill/references/classification.md ## Task Workflow **URL:** `$1` ### Step 0: Find Vault 0. Look for `.distill-state.yaml` in the current directory, then `~/Obsidian/Insights/`. If not found, ask the user for the vault path. ### Step 1: Fetch 1. WebFetch the URL. If it fails, report the error and ask if the user wants to classify based on title alone. (WebFetch is fine for single URLs - the curl approach is only needed for batch scraping.) ### Step 2: Classify ...
Read the skill definition for output formats and classification criteria:
URL: $1
.distill-state.yaml in the current directory, then ~/Obsidian/Insights/. If not found, ask the user for the vault path.classification.md.If insight:
Verdict: insight ({confidence})
Summary: {one-line insight summary}
Concepts: {tags}
Topic: {proposed folder}
If noise:
Verdict: noise
Reason: {why it doesn't meet the insight bar}
If unclear:
Verdict: borderline
For: {what makes it potentially insightful}
Against: {what makes it potentially noise}
If user says yes to insight:
.distill-state.yaml for vault path{vault}/{topic}/{filename}.mdIf user says yes to noise:
{vault}/_noise.md: - [Title](url) — noise: {reason}If user says ignore: do nothing.
npx claudepluginhub cjhwong/claude-skills --plugin distill/checkRuns project validation checks like lint/test across JavaScript/TypeScript, Python, Go, Rust, Ruby and auto-fixes errors without committing changes.
/checkRuns project validation checks like lint/test across JavaScript/TypeScript, Python, Go, Rust, Ruby and auto-fixes errors without committing changes.
/checkDetects drift between SPEC.md and source code, classifying items as HOLD/VIOLATE/UNVERIFIABLE (or MATCH/DRIFT/MISSING/EXTRA for interfaces) with file:line evidence and remedy hints. Read-only, writes nothing.
/checkRuns a unified pre-publish quality gate on marketing content, scoring across hallucination, brand voice, structure, and claims dimensions. Returns a pass/warn/blocked decision with fix suggestions.
/checkGenerates CodeDNA coverage report for the project, identifying unannotated source files and stale used_by references in Python, TypeScript/JS, Go, Rust, Java.
/checkChecks spec-kit CLI (uv and specify) installation status and project setup (.specify/ directory), outputs ✅/❌ results with install guides and next steps.