video-note

Transform Obsidian video notes from the Vault into published notes on joelclaw.com. Use when publishing video notes, converting vault video content to the site, or when asked to 'publish a video note,' 'turn this video into a note,' 'publish from vault/videos,' or any task involving /Vault/Resources/videos → joelclaw content. Triggers on references to video notes, vault video files, or publishing video content to the blog.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, mostly actionable skill body with good progressive disclosure and lean prose. Its main weakness is the workflow: the publish step sequence lacks any explicit validation or verification checkpoint before writing the published note.

Suggestions

Add a verification step to the workflow before publishing — e.g., confirm the slug is kebab-case and unique in apps/web/content/, validate required frontmatter fields, and check the .mdx builds.

Tighten the 'Voice reference' section by relying more on the joel-writing-style pointer and keeping only the one or two rules most likely to be missed, reducing overlap with workflow step 3.

Include a one-line inline example of an actual slug transformation (source title → final slug) so the slug rule is copy-paste concrete rather than illustrative.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids explaining Obsidian/markdown basics, but the Voice reference section mildly repeats rules already implied by the joel-writing-style pointer and could be trimmed slightly.	4 / 5
Actionability	Provides concrete frontmatter specs for source and output, exact paths (apps/web/content/), the embed component, slug format, and a section-by-section mapping; minor abstraction remains in 'rewrite as the intro (Joel's voice)' without an inline worked example.	4 / 5
Workflow Clarity	The 7-step sequence is clearly ordered, but there is no validation or verification checkpoint (e.g., confirm frontmatter validity, check slug uniqueness, verify the MDX builds) before publishing, which is an implicit validation gap.	3 / 5
Progressive Disclosure	SKILL.md is a concise overview with well-signaled, one-level-deep references to real files (references/content-system.md, references/example-note.md) plus a pointer to the sibling joel-writing-style skill, making navigation easy.	5 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states the single purpose, uses natural third-person trigger phrasing, and is highly distinguishable from other skills. Its only limitation is that the several action verbs describe one core transformation rather than a broad multi-action capability.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete source→target transformation ('Transform Obsidian video notes from the Vault into published notes on joelclaw.com') with several action verbs (transform/convert/publish), though they are variations of one core action rather than comprehensive multi-action coverage.	4 / 5
Completeness	Explicitly answers both what ('Transform…into published notes on joelclaw.com') and when ('Use when…', 'Triggers on…') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural user phrasings as quoted triggers — 'publish a video note,' 'turn this video into a note,' 'publish from vault/videos' — plus synonyms like 'video notes,' 'vault video files,' giving comprehensive natural-term coverage.	5 / 5
Distinctiveness Conflict Risk	A highly specific niche (Obsidian vault videos → joelclaw.com) with distinct, narrow triggers makes overlap with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: joelhooks/joelclaw
Path: skills/video-note/SKILL.md
Commit: 7094ced

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.