omg

I checked out your skill and noticed the core logic is solid, but the documentation could use some work to help developers understand the intended use cases—especially since the grade came back at 73.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 73/100, which puts you in C territory — solid fundamentals, but there's some low-hanging fruit to bump this up. Based on Anthropic's best practices for agentic skills, your Spec Compliance is strong (12/15), but Ease of Use and Utility are dragging things down. The biggest gap is workflow guidance and examples.

What's Working Well

• Metadata is sharp. Your description nails the trigger with "writing or editing .omg.md files" and explains purpose clearly.
• Spec compliance is clean. Valid YAML frontmatter, correct naming conventions, and you're hitting 12 out of 15 points here.
• Concise structure. At 48 lines, the skill is lean and doesn't bloat with unnecessary content—you earned points for that.

The Big One: Missing Workflow Guidance

Here's what's holding you back: developers don't know how to actually use this thing end-to-end. You list code block types (omg.path, omg.body, omg.response) but never show developers the decision tree—when do you use each? What's the structure of a complete endpoint?

The fix: Add a section called "Endpoint Structure Checklist" that walks through:

1. Define method/path in frontmatter
2. Use omg.path for parameters
3. Use omg.body for POST/PATCH payloads
4. Use omg.response for 200 success
5. Use omg.response.400 for errors

This alone could add ~3 points and makes the skill immediately more useful.

Other Things Worth Fixing

1. Only one example. You've got a single GET endpoint. Add a references/examples.md with POST (including body val...