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.

1.73x

Quality

88%

Does it follow best practices?

Impact

99%

1.73x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

87%Weight 40%Scale 1-3

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

A tight, actionable skill body that front-loads concrete formats and a clear workflow while pushing detail to well-signaled reference files; its main gap is the absence of an explicit validation step in the publish workflow.

Suggestions

Add a verification step to the workflow (e.g., check the slug does not already exist under apps/web/content/ and confirm required frontmatter fields are present before writing the .mdx file).

Collapse the overlap between step 3's writing-voice rules and the 'Voice reference' section to avoid restating style guidance twice in the body.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence: it gives exact frontmatter, paths, and embed syntax without explaining what Obsidian or MDX is, and every section earns its tokens.	3 / 3
Actionability	Guidance is concrete and copy-ready — specific vault and output paths, full frontmatter blocks, the <YouTube id="…" /> embed, and a slug rule — with no vague abstraction.	3 / 3
Workflow Clarity	The 7-step transformation workflow is clearly sequenced, but there is no validation or verification checkpoint (e.g., confirm the slug is unused, verify frontmatter) for the publish/write operation, so it sits at the 'sequence present but checkpoints missing' anchor rather than the top.	2 / 3
Progressive Disclosure	The body is a concise overview pointing one level deep to real, clearly signaled references (references/content-system.md and references/example-note.md), with detail appropriately split out.	3 / 3
	Total	11 / 12 Passed

Description

90%Weight 40%Scale 1-3

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, well-scoped description with explicit 'what' and 'when' guidance and natural trigger terms; its only weakness is that it frames a single transformation workflow rather than enumerating several concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('Obsidian video notes from the Vault' → 'published notes on joelclaw.com') and the core transform/publish action, but describes essentially one workflow rather than multiple distinct concrete actions, so it falls short of the 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	Explicitly answers what it does (transform vault video notes into published joelclaw.com notes) and when to use it via an explicit 'Use when…' clause with multiple triggers, matching the top anchor.	3 / 3
Trigger Term Quality	Quotes several natural phrases a user would actually say — 'publish a video note', 'turn this video into a note', 'publish from vault/videos' — giving good coverage of likely trigger language.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and tied to a specific vault path and target site with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: 979b138

Reviewed: 10 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.