outbound-plays

I found your skill while evaluating the latest batch—the outbound-plays approach is solid, but I'm curious why you went with that particular pattern for handling the workflow orchestration when there seem to be some edge cases in the current implementation (you're sitting at a 65/100).

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 65/100, D territory—which is workable but leaves real points on the table. This is based on Anthropic's skill grading standards. Your strongest area is Spec Compliance (11/15) with solid YAML frontmatter and naming conventions, but Utility (12/20) and Ease of Use (17/25) are dragging things down. The gap mostly comes from missing concrete examples and fuzzy execution instructions.

What's Working Well

• Clean structure – Your YAML frontmatter is valid and follows conventions perfectly. The hyphen-case naming (outbound-plays) is correct.
• Real problem you're solving – The Framework section correctly identifies an actual GTM workflow pain: tying intent signals to outreach timing. That's legitimate utility.
• Numbered steps – Your 1-4 framework progression (Trigger Mapping → Content Adaptation → Execution → Measurement) shows you thought about logical flow.

The Big One: Missing Templates and Concrete Examples

Here's what's holding you back: you list templates in your Templates section but don't provide them. You say "Trigger-to-play matrix (signal, persona, playbook, assets needed)" but show zero examples. A user reading this skill has no idea what a filled-in trigger-to-play matrix actually looks like.

Why it matters: Without examples, your skill is conceptual guidance masquerading as executable. Users can't validate they're doing it right, and they'll bounce to find reference implementations elsewhere.

The fix: Create two reference files:

• references/trigger-to-play-matrix-template.md – Show 3-4 example rows with real GTM signals (e.g., "Security audit initiated → exec briefing play → CMO + security VP")
• references/sequence-script-example.md – Provide actual email/call scripts that reference signals, not just descriptions of what scripts should contain

That alone bumps you +5 points on Utility (examples/templates +3, problem-solving power +2).

Other Things Worth Fixing

1. Framework steps need checklists, not categories – "Trigger Mapping" should become a checklist: □ Extract signals from intent data □ Classify by buying stage □ Match to archetype using [decision tree] □ Validate signal freshness (<7 days). Right now it's conceptual. Make it executable. (+3 points)

2. Inconsistent voice – Your "When to Use" section mixes gerunds ("Launching targeted SDR/AE campaigns", "Coordinating multi-channel waves") with imperative elsewhere. Pick one form and stick with it. "Launch" instead of "Launching". (+2 points)

3. Terminology confusion: play vs. playbook – You use both interchangeably without defining them. Add upfront: "A play is a single outreach sequence; a playbook is a collection of plays." This clears up navigation. (+2 points)

4. Add trigger phrases to description – Your frontmatter description has no trigger keywords. Change it to mention "outbound plays" explicitly so the skill surfaces when users search. (+2 points)

Quick Wins

• Biggest bang: Create the two template reference files (trigger matrix + example script) = +5 points
• Next: Convert Framework steps into actionable checklists = +3 points
• Style fixes: Consistent voice (gerund → imperative) + define play/playbook upfront = +4 points
• Metadata: Add trigger phrases to description = +2 points

That's +14 points if you execute. You could be pushing 79/100 with focused work.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.