senior-computer-vision

Took a look at your computer vision skill — the domain coverage is solid, but the spec could use some tightening to really guide users through the complexity here. What's the core problem you're trying to solve with this one?

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 45/100, firmly in F territory. This is graded against Anthropic's best practices for agentic skills. Your strongest area is Spec Compliance (12/15) — the frontmatter and naming conventions are solid. But Utility (6/20) is dragging you down hard. The skill reads generic instead of vision-specific, and the reference files are basically identical boilerplate.

What's Working Well

• Valid YAML structure — Your frontmatter is clean and follows conventions properly
• Consistent naming — senior-computer-vision uses proper hyphen-case formatting
• Grep-friendly structure — The skill has decent header organization for searchability

That said, these are table-stakes stuff. You need the substance to back them up.

The Big One: Zero Computer Vision Content

Here's the core problem: you've built a computer vision skill that contains almost zero actual computer vision content. You've got 227 lines talking about "world-class senior professionals" and generic MLOps, but nothing about CNNs, object detection models, segmentation architectures, or vision-specific optimization techniques.

Why this matters: When someone invokes this skill, they're asking for help with vision problems — not data engineering platitudes. The skill should guide them on YOLO architectures, Transformer-based detection (DETR), segmentation models (Mask R-CNN, SAM), video analysis, 3D vision. Right now it's indistinguishable from a generic ML skil...