reward-ops

I was curious what a skill for managing reward operations would look like—turns out you've built something that tackles a genuinely tricky domain, though the execution could use some tightening around the Progressive Disclosure architecture to really sing.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 68/100, which is D territory—needs work, but salvageable. This is based on Anthropic's skill best practices. Your strongest area is Spec Compliance (11/15), but Utility (11/20) is dragging you down hard. The gap between what you describe and what you actually deliver is the real problem here.

What's Working Well

• Valid YAML structure – Frontmatter is clean and follows conventions correctly
• Clear operational scope – You've identified a real domain problem (catalog management, fulfillment, vendor coordination)
• Organized framework – The five-point structure (Governance, Fulfillment, Vendor Integration, Compliance, Monitoring) is logical and shows you've thought through the problem space
• grep-friendly formatting – Got a bonus point for structure that's easy to parse

The Big One: Missing Reference Files

Here's what's killing your utility score: you mention templates and runbooks that don't exist. You say "Templates: Reward catalog spreadsheet... Fulfillment flowchart... Incident log + RCA template" but none of these are actually provided. This creates a gap where developers read your skill and think "okay, but where do I start?"

The fix: Create a references/ directory alongside SKILL.md with actual files:

• catalog-template.md – Sample SKU metadata structure
• fulfillment-flowchart.md – Visual or text-based workflow
• incident-rca-template.md – Incident response template ...