scrum-master-agent

I took a look at your scrum-master-agent skill—the 68-point score reflects some solid foundational work, but there's a gap between what the skill could do and what it actually delivers. You've got the bones of something useful for agile teams, but the Progressive Disclosure architecture needs some rethinking to make it genuinely intuitive for developers who just want to run it without reading a manual.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 68/100, which puts you in D territory. This is based on Anthropic's Progressive Disclosure Architecture standards—basically, how efficiently your skill uses developer tokens while remaining discoverable and usable. Your Utility scores strong at 15/20 (the skill actually solves real Scrum Master problems), but Writing Style drags you down hard at 4/10 (marketing language everywhere). The real issue isn't what the skill does—it's how it presents what it does.

What's Working Well

• Utility is genuinely solid. Your sprint calculations, capacity planning, and multi-tool integration (Linear, Jira, GitHub) address real workflow gaps. The skill solves concrete problems.
• Your examples in HOW_TO_USE.md are strong. Sample data files and concrete workflows show you've thought about real usage patterns.
• Clear scope boundaries. The skill knows what it does and doesn't do—that's worth +1 modifier bonus and saves developers from guessing.

The Big One: Marketing Language is Killing Your Objectivity Score

Your SKILL.md reads like sales copy instead of technical documentation. Phrases like "production-ready," "intelligent," "comprehensive," and "ultra-lightweight" aren't describing what your skill does—they're selling it. Line 8, ...