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 known issues

Quality

Content

87%

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

This is a well-crafted skill that efficiently communicates a specific publishing workflow with concrete schemas, clear transformation steps, and good progressive disclosure to supporting references. Its main weakness is the lack of validation/verification steps in the workflow — there's no checkpoint to confirm the MDX output is valid or renders correctly before considering the task complete. Overall it's a strong skill that respects Claude's intelligence while providing the domain-specific details needed.

Suggestions

Add a validation step after writing the MDX file (e.g., check frontmatter has all required fields, verify the YouTube component ID is correct, confirm no residual Obsidian syntax remains)

Consider adding a brief 'common mistakes' or 'gotchas' note — e.g., forgetting to strip wikilinks, leaving transcript in, or malformed MDX frontmatter

Dimension	Reasoning	Score
Conciseness	Every section earns its place — source format, output format, transformation steps, and references are all specific to this workflow. No unnecessary explanations of what Obsidian or MDX are. The content is dense with actionable detail without padding.	3 / 3
Actionability	Provides concrete frontmatter schemas for both input and output, a specific 7-step transformation workflow with clear sub-instructions (e.g., strip Obsidian syntax, embed YouTube component, slug format), and references to style guides and examples. The guidance is specific enough to execute without ambiguity.	3 / 3
Workflow Clarity	The 7-step workflow is clearly sequenced and covers the transformation well, but there are no validation checkpoints — no step to verify the MDX renders correctly, no check that frontmatter is valid, no feedback loop for catching errors before publishing. For a content publishing workflow, a validation step would be important.	2 / 3
Progressive Disclosure	Excellent structure: the SKILL.md provides a complete overview with well-signaled one-level-deep references to joel-writing-style skill, voice examples, content-system.md, and example-note.md. Content is appropriately split between the overview and supporting files.	3 / 3
	Total	11 / 12 Passed

Description

89%

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

This is a strong skill description with excellent trigger term coverage and completeness, clearly specifying both what the skill does and when to use it. Its main weakness is that the core capability is somewhat singular—it describes one transformation action rather than listing multiple concrete sub-actions involved in the process. The description is highly distinctive and unlikely to conflict with other skills.

Suggestions

Add more specific concrete actions involved in the transformation process (e.g., 'extracts video metadata, formats transcript content, generates frontmatter, creates blog-ready markdown') to improve specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain (Obsidian video notes, Vault, joelclaw.com) and the core action (transform/publish), but it doesn't list multiple specific concrete actions like extracting metadata, formatting markdown, generating frontmatter, etc. It's essentially one action described in different ways.	2 / 3
Completeness	Clearly answers both 'what' (transform Obsidian video notes from the Vault into published notes on joelclaw.com) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios and a 'Triggers on' clause). Both dimensions are well-covered.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'publish a video note,' 'turn this video into a note,' 'publish from vault/videos,' 'video notes,' 'vault video files,' 'publishing video content to the blog,' and the specific path '/Vault/Resources/videos.' These are phrases a user would naturally say.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a very specific niche: Obsidian Vault video notes → joelclaw.com. The specific source path (/Vault/Resources/videos), target site (joelclaw.com), and content type (video notes) make it extremely unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: joelhooks/joelclaw
Commit: 2ca3686

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.