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