senior-devops

I've been looking through skills in the infrastructure space, and I noticed your senior-devops skill takes on some pretty heavy lifting—orchestrating deployments, handling multi-environment configs, that kind of thing. The score suggests there's real potential here, but it looks like the spec and structure might need some refinement to really land for users.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 36/100, which puts this in F territory. This is based on Anthropic's Progressive Disclosure Architecture rubric for agentic skills. Your strongest area is Spec Compliance (12/15)—the frontmatter is valid and properly formatted. But Utility (2/20) is where things fall apart. The scripts and reference guides are basically placeholder templates with no actual DevOps functionality baked in.

What's Working Well

• Spec compliance is solid - Your YAML frontmatter is valid, naming conventions are correct (hyphen-case), and you've got the required metadata fields in place.
• Breadth of trigger coverage - You've listed relevant DevOps triggers like "setting up pipelines," "infrastructure as code," and "deploying applications"—good instinct on what users would search for.
• Structure exists - You've got the reference file architecture (IaC guide, CI/CD pipeline guide, deployment strategies), which shows you thought about Progressive Disclosure.

The Big One: Non-Functional Scripts

Here's the thing—all three Python scripts in scripts/ are identical placeholder templates. They don't actually generate pipelines, scaffold Terraform, or manage deployments. They just return empty self.results['findings'] = [].

This is a massive credibility killer. When someone invokes this skill expecting DevOps automation, ...