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.
91
88%
Does it follow best practices?
Impact
99%
1.73xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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. It clearly defines when to use the skill with multiple natural phrasings and explicit path references. The main weakness is that the 'what' portion could be more specific about the concrete transformation steps involved beyond the high-level 'transform and publish' action.
Suggestions
Add 2-3 specific sub-actions to increase specificity, e.g., 'Extracts video metadata, formats transcript content, generates frontmatter, and publishes as a blog post on joelclaw.com.'
| 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 clear niche: specifically video notes from a specific Vault path to a specific site (joelclaw.com). The combination of Obsidian Vault, video notes, and the target blog makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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 clearly defines the transformation pipeline from Obsidian vault notes to published MDX content. It's concise, actionable, and well-structured with appropriate references to supporting materials. The main gap is the lack of validation/verification steps in the workflow — there's no checkpoint to confirm the output MDX is valid or renders correctly before considering the task complete.
Suggestions
Add a validation step after writing the MDX file (e.g., check frontmatter has all required fields, verify the YouTube component ID is valid, confirm the file renders without errors).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place — source format, output format, transformation steps, and references are all necessary and tightly written. No unnecessary explanations of what Obsidian or MDX are; assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides concrete frontmatter schemas for both input and output, specific transformation rules (e.g., 'Executive summary → rewrite as intro'), exact component syntax (`<YouTube id="VIDEO_ID" />`), and clear slug conventions. Each step is specific enough to execute directly. | 3 / 3 |
Workflow Clarity | The 7-step transformation workflow is clearly sequenced and covers the full pipeline. However, there are no validation checkpoints — no step to verify the MDX renders correctly, check frontmatter validity, or confirm the slug doesn't conflict with existing content. For a publishing workflow that creates files, a validation step would be expected. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure: the SKILL.md provides a complete overview with clear one-level-deep references to the writing style skill, voice examples, content system details, and an example note. References are well-signaled with descriptive link text and relative paths. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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
825972c
- Reviewed
Table of Contents
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.