program-ops

I was browsing through some skill implementations and noticed yours focuses on program operations—curious how you're handling the orchestration layer, since that's where a lot of complexity tends to hide. Took a closer look at the structure and wanted to share some observations from the evaluation.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 54/100, which puts you in F territory—meaning this needs some real work before it's marketplace-ready. The evaluation's based on Anthropic's skill best practices. Your strongest area is Spec Compliance (12/15), which tells me the file format is dialed in. But Utility (8/20) and Progressive Disclosure Architecture (12/30) are dragging the score down hard.

What's Working Well

• Clean frontmatter – Your YAML is valid and properly formatted; the name follows hyphen-case conventions correctly
• Consistent terminology – You stick with terms like "workflow," "tool stack," and "vendor management" throughout, which makes the content coherent
• Real problem space – The framework addresses actual event operations challenges (intake → approval → production → execution → follow-up), so you're not solving hypothetical stuff

The Big One

Your skill is 31 lines in a single flat file with zero supporting materials. That's the core problem. You mention "SOP library," "templates," and "tool stack guidance," but then provide absolutely nothing—no reference files, no examples, no actual templates. It reads like an outline instead of a usable skill.

Here's the fix: Create a references/ folder with depth:

• references/workflow-map.md – Detailed step-by-step for each workflow phase (not just arrows)
• references/templates.md – Actual SOP templates (registration setup,...