senior-backend

I noticed you're building something for senior backend engineers, but the grading suggests the skill might be trying to cover too much ground—hard to deliver deep value when you're targeting both architecture patterns and day-to-day tooling at once.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 33/100, which puts you in F territory. This is based on Anthropic's Progressive Disclosure Architecture standards for agentic skills. Your strongest area is Spec Compliance (12/15)—the YAML frontmatter is clean and well-structured. The biggest drag is Utility (3/20)—the skill references fictional scripts and placeholder content that don't actually solve problems.

What's Working Well

• Clean frontmatter: Your YAML is valid with all required fields and good trigger terms (NodeJS, Express, GraphQL, Microservices)
• Metadata comprehensiveness: The description covers a good range of backend concerns and uses specific technology keywords for discoverability
• Structural compliance: You're following the skill format correctly—name conventions, file organization, reference structure

The Big One: Fictional Scripts Kill Utility

This is your main blocker. The skill references three Python scripts that don't exist:

• api_scaffolder.py
• database_migration_tool.py
• api_load_tester.py

These appear as placeholders with [options] parameters but no actual implementation or guidance on using real tools (npm, psql, curl, ab, etc.). Fix this by either:

1. Creating actual working scripts with real examples, or
2. Removing script references and teaching Claude to use standard backend tooling directly with specific commands and workflows

This alone could add +6 points to your score.

Other Things Worth Fixi...