senior-fullstack

I've been looking at how this skill handles the full stack perspective—there's definitely some interesting ground being covered, but the execution seems to be pulling in too many directions at once. Given the F rating, I'd love to understand what the core focus was supposed to be, because senior-level work usually benefits from a tighter scope.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 31/100, solidly F territory. This is based on Anthropic's skill evaluation best practices. Your strongest area is Spec Compliance (12/15)—the metadata and frontmatter are clean. But Utility is barely there (2/20), and that's what actually matters to developers using this thing.

What's Working Well

• Valid YAML frontmatter - You've got the metadata structure right with proper name conventions
• Trigger phrases included - The description mentions "building new projects" and "code quality" as entry points
• File organization exists - Three reference files show you're thinking about layered documentation
• Scripts are referenced - The skill mentions specific automation tools that could be useful

The Big One: Placeholder Content Killing Your Utility Score

This is what's tanking you. All three reference files—development_workflows.md, tech_stack_guide.md, and architecture_patterns.md—contain identical generic placeholder content. We're talking about lines like:

Pattern 1: Best Practice Implementation
Description: Detailed explanation of the pattern.
When to Use: Scenario 1, Scenario 2, Scenario 3

No actual patterns. No real code. No specifics. A senior fullstack developer looking at this skill gets nothing actionable.

The fix: Replace these with real patterns. Instead of "Pattern 1," w...