CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 instruction-only skill: lean, concrete, and clearly sequenced, with appropriate use of reference files. The gaps are a missing post-write validation step, slight duplication of delegated voice rules, and two cross-skill links that don't resolve.

Suggestions

Add a final workflow step to validate the output (e.g., confirm frontmatter fields match the site's expected schema in references/content-system.md and the MDX builds) — this would raise workflow_clarity.

Make the joel-writing-style dependency robust: either inline the essential voice rules once and drop the duplicated bullet list, or verify the `../joel-writing-style/` relative links resolve from wherever this skill is installed.

State the output filename convention explicitly (e.g., `apps/web/content/<slug>.mdx`) so step 7's slug has an unambiguous destination.

DimensionReasoningScore

Conciseness

The body is lean with concrete templates and no explanations of concepts Claude already knows. Not 5 because the "Voice reference" section re-lists style rules already delegated to the joel-writing-style skill, which could be trimmed to a pointer.

4 / 5

Actionability

Concrete guidance throughout: source/output frontmatter templates, `<YouTube id="VIDEO_ID" />`, the slug example `openclaw-peter-steinberger-lex-fridman`, and a section-by-section mapping. Not 5 because voice execution is delegated to a sibling skill reference and the output filename convention beyond the slug is only implied.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with an explicit exclusion gate ("Exclude the full transcript, private context, customer information"). Not 5 because there is no validation checkpoint after writing (e.g., confirm the MDX renders or frontmatter matches the site's expected types).

4 / 5

Progressive Disclosure

Two clearly signaled, one-level-deep references (`references/content-system.md`, `references/example-note.md`) that both exist, and the body stays a concise overview. Not 5 because the cross-skill links `../joel-writing-style/SKILL.md` and `../joel-writing-style/references/voice-examples.md` do not resolve from this bundle.

4 / 5

Total

16

/

20

Passed

Description

90%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 description with explicit what/when structure and excellent natural trigger phrases. Its only weakness is that the capability list stops at a single transformation action rather than enumerating the concrete steps it performs.

DimensionReasoningScore

Specificity

"Transform Obsidian video notes from the Vault into published notes on joelclaw.com" names the domain and one concrete transformation action; the restatement "converting vault video content to the site" is the same action, not additional ones. Not 4 because it does not list several distinct capabilities (extraction, MDX formatting, voice rewriting appear only in the body).

3 / 5

Completeness

Explicitly answers what ("Transform Obsidian video notes from the Vault into published notes on joelclaw.com") and when ("Use when publishing video notes... or when asked to...") with concrete trigger phrases. Matches the anchor-5 good example structure exactly.

5 / 5

Trigger Term Quality

Quoted natural phrases like "publish a video note," "turn this video into a note," and "publish from vault/videos" alongside "video notes, vault video files, publishing video content" give comprehensive coverage of what a user would actually say. Not below 5 — no common variation is obviously missing for this niche.

5 / 5

Distinctiveness Conflict Risk

A highly specific Obsidian-vault-to-joelclaw.com pipeline with distinct triggers (vault videos, publishing video notes) that no generic skill would claim. Third-person voice throughout; no overlap risk apparent.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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
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.