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, badge printing, onsite checklists)
• references/tool-stack.md – Specific vendor evaluation criteria and scoring

Keep SKILL.md as the concise entry point, but move all the meat into references. This alone bumps you +8 points.

Other Things Worth Fixing

1. Weak trigger terms – Your description says "standardizing event workflows" but that's too generic. Add concrete triggers like "event operations audit," "ops standardization," "vendor management," "SOP library" so the skill actually activates when people need it (+4 points)

2. No actionable procedures – Your framework lists categories but doesn't tell someone how to do them. Turn each workflow phase into numbered steps with decision criteria. Example: "Intake: 1. Capture request via form. 2. Validate budget code. 3. Assign owner within 24h"

3. Missing validation steps – You never explain how to verify success or troubleshoot. Add "Verify" and "Fix" sections to each workflow phase so people know what working looks like (+3 points)

4. Inconsistent voice – You mix noun phrases ("Workflow Map – intake → approval") with imperative verbs ("Automate reminders"). Standardize to imperative throughout for clarity

Quick Wins

• Create references/ folder with 3 supporting docs (biggest impact)
• Rewrite trigger terms in the description to be specific and concrete
• Turn framework sections into numbered step-by-step procedures
• Add a "Verify" or "Check" line to each workflow phase

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.