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.
95
95%
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 specific path references. The main weakness is that the 'what' portion could be more specific about the concrete transformation steps involved rather than just stating the high-level action of transforming/publishing.
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
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently describes a specific content transformation pipeline. It provides exact input/output formats, a clear multi-step workflow, and well-organized references to supporting materials without over-explaining. The content is lean, actionable, and well-structured for Claude to follow.
| 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 concepts Claude already knows (no explaining what MDX is, what Obsidian is, etc.). | 3 / 3 |
Actionability | The workflow provides concrete, specific steps: exact file paths, exact frontmatter schemas for both input and output, specific transformation rules (e.g., 'Executive summary → rewrite as intro'), specific component syntax (`<YouTube id="VIDEO_ID" />`), and slug format examples. Fully actionable. | 3 / 3 |
Workflow Clarity | The 7-step transformation workflow is clearly sequenced with specific sub-steps. Each step maps a source element to a target transformation. The process isn't destructive (it's creating new files from existing ones), so heavy validation checkpoints aren't critical, and the sequence is unambiguous. | 3 / 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 | 12 / 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
ce9ca8e
- 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.