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.
81
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/skills-catalog/skills/(gtm)/video-outreach/SKILL.mdQuality
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 description with excellent trigger term coverage and completeness, including both positive triggers and explicit exclusions. Its main weakness is that the 'what it does' portion relies on somewhat high-level category descriptions rather than listing specific concrete actions the skill performs. The trigger terms and tool names make it highly distinctive and unlikely to conflict with other skills.
Suggestions
Replace high-level phrases like 'video-first outreach systems from personalization through conversion optimization' with specific concrete actions such as 'write video outreach scripts, design multi-touch video sequences, select video platforms, optimize video email subject lines, and track video engagement metrics.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (video-first cold outreach) and mentions some actions like 'build video-first cold outreach,' 'create personalized video at scale,' 'implement async selling,' and 'AI demo generation,' but these are more like category labels than concrete, specific actions. It lacks granular actions like 'write video scripts,' 'design outreach sequences,' or 'optimize conversion rates.' | 2 / 3 |
Completeness | The description clearly answers both 'what' (video-first outreach systems from personalization through conversion optimization) and 'when' (explicit 'Use when' triggers and a helpful 'Do NOT use' exclusion clause). The trigger guidance is explicit and well-structured. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including tool names ('Tavus,' 'Sendspark,' 'HeyGen'), user phrases ('video outreach,' 'personalized video,' 'video prospecting,' 'video email,' 'async selling,' 'video demo'), and even the colloquial phrase 'made this for you.' These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a very clear niche around video-based sales outreach with specific tool names and domain-specific terminology. The 'Do NOT use' clause further reduces conflict risk by explicitly excluding technical implementation and code review tasks. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at actionability and workflow clarity, providing genuinely useful frameworks like the 'Made This For You' process, time-stamped video scripts, and watch-time-based follow-up actions. However, it is severely over-length with significant verbosity—platform marketing stats, basic recording tips (lighting, framing), and explanations of concepts Claude already understands inflate the token count substantially. The content would benefit greatly from splitting detailed platform comparisons and benchmarks into separate reference files.
Suggestions
Cut the content by 40-50%: remove platform marketing stats (e.g., 'Named #1 Fastest Growing Product of 2025 on G2'), basic recording tips (lighting, framing, audio), and explanatory text Claude doesn't need. Keep the decision frameworks and actionable templates.
Move platform comparison tables, conversion benchmarks, and tech stack tiers into separate reference files (e.g., PLATFORMS.md, BENCHMARKS.md) and link to them from the main skill.
Remove or condense the 'Before Starting' discovery questions section—Claude knows how to ask qualifying questions; a brief note like 'Qualify: volume, deal size, existing stack, budget, goal' suffices.
Remove time-sensitive claims like '2025-2026' patterns and specific pricing that will quickly become outdated, or explicitly mark them as potentially outdated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~500+ lines. It explains concepts Claude already knows (what async selling is, what thumbnails are, basic lighting tips), includes extensive platform marketing copy with stats that may be outdated, and repeats similar information across sections. The platform comparison tables, while useful, contain promotional language and could be condensed significantly. | 1 / 3 |
Actionability | The skill provides highly concrete, actionable guidance throughout: specific time-stamped video scripts (60-second formula, 3-minute async demo), exact sequence architectures with day-by-day actions, specific tool recommendations with pricing, decision trees for tool selection, and clear examples of deliverables by buyer role. The guidance is copy-paste ready for sales execution. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit checkpoints. The 'Made This For You' four-step process, the sales sequence architecture (Day 1-15), the watch-time qualification signal table with follow-up actions, and the async demo structure all provide clear workflows with decision points and feedback loops (e.g., watch % triggers specific follow-up actions). | 3 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files for detailed content. The platform comparisons, recording best practices, and conversion benchmarks could each be separate reference files. The Related Skills section at the end provides good cross-references, but the main body contains too much inline detail that should be split out. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
81e7e0d
Table of Contents
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.