video-outreach

When the user wants to build video-first cold outreach, create personalized video at scale, implement async selling, or use AI demo generation for prospecting. Also use when the user mentions 'video outreach,' 'personalized video,' 'video prospecting,' 'Tavus,' 'Sendspark,' 'HeyGen,' 'video email,' 'async selling,' 'video demo,' or 'made this for you.' This skill covers video-first outreach systems from personalization through conversion optimization. Do NOT use for technical implementation, code review, or software architecture.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

The body is a thorough, actionable reference with clear workflows and feedback loops, but it is monolithic and over-long, bundling material that would benefit from split reference files and trimming common-sense padding. Strong on actionability and workflow clarity, weaker on conciseness and progressive disclosure.

Suggestions

Trim or remove common-sense padding Claude already knows — e.g. the 'Lighting and Framing' bullets and generic items in 'Common Mistakes' — to lift conciseness.

Split the large reference material (Platform Comparison, Conversion Benchmarks, Tech Stack tiers) into one-level-deep bundle files under references/ and link to them from a leaner SKILL.md overview to improve progressive disclosure.

Move the 'Measuring Performance' metrics tables and 'Questions to Ask' into a separate reference file so SKILL.md stays a focused overview pointing to detail.

Dimension	Reasoning	Score
Conciseness	Largely specific and information-dense, but padded with common-sense guidance Claude already knows ('Face the light source,' 'Bad audio kills engagement faster than bad video. Use a decent mic') and an 8-item 'Common Mistakes' list that could be trimmed.	2 / 3
Actionability	Highly actionable for an instruction-only skill: time-stamped video segments, copy-ready subject-line templates ('[Name], built a [deliverable] for [Company]'), a Day 1–15 sequence, and concrete priced tool tiers — no code needed but the guidance is specific and copy-ready.	3 / 3
Workflow Clarity	The four-step process and Day 1–15 sequence are clearly ordered, and feedback loops exist via the Watch-Time signal table (watch % → follow-up action) and the Troubleshooting section.	3 / 3
Progressive Disclosure	A monolithic ~450-line file with no bundle references; content that would fit separate files (tool landscape, conversion benchmarks, recording tips) is inline despite well-organized section headers.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

The description is specific, trigger-rich, and clearly scopes both when to use and when not to use the skill, with a distinct niche and explicit negative boundary. It is a strong, well-constructed skill description.

Dimension	Reasoning	Score
Specificity	Lists several distinct concrete actions — 'build video-first cold outreach, create personalized video at scale, implement async selling, or use AI demo generation' — matching the multiple-specific-actions anchor rather than the single-action level 2.	3 / 3
Completeness	Explicitly answers both 'what' (build/create/implement/use) and 'when' via an 'Also use when the user mentions …' clause, plus a 'Do NOT use for' exclusion, satisfying the explicit-trigger bar.	3 / 3
Trigger Term Quality	Strong natural-language trigger coverage ('video outreach,' 'personalized video,' 'video prospecting,' 'Tavus,' 'Sendspark,' 'HeyGen,' 'async selling,' 'made this for you') — terms a user would plausibly say.	3 / 3
Distinctiveness Conflict Risk	A clear video-outreach niche with vendor-specific triggers and an explicit negative-scope boundary makes triggering for the wrong skill unlikely; voice is impersonal third person with no first/second-person penalty.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tech-leads-club/agent-skills
Commit: 9026164

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