I took a look at your generating-stored-procedures skill and wanted to share some thoughts.
Links:
The TL;DR
You're at 34/100, which puts you in F territory. This is based on Anthropic's 5-pillar rubric for skill quality. Your strongest area is Spec Compliance (14/15) - the frontmatter is solid. But you're getting crushed on Utility (3/20) and Progressive Disclosure (8/30). The core problem: this skill reads like a generic DevOps checklist, not a stored procedure expert.
What's Working Well
- Spec Compliance is tight - Your YAML frontmatter is valid, naming conventions are correct, and you're following the structural requirements
- Description triggers are present - You've got phrases like "generate stored procedures" and "create database functions" in there
- License included - Nice touch with the optional field
The Big One
Your skill is entirely generic. The 5-step workflow ("Assess Current State," "Review configuration") applies to literally any task. You promise PostgreSQL, MySQL, and SQL Server guidance in the description, but deliver absolutely nothing database-specific. Step 1 says "Review current configuration" - what configuration? There's no stored procedure context here.
The fix: Rewrite those 5 steps to be procedure-specific. Instead of "Assess Current State," do "Analyze Schema" - identify tables, define input parameters, document transaction requirements. Add actual CREATE PROCEDURE examples for each database. Create the reference files you're promising (postgresql_stored_procedure_best_practices.md, etc.). This alone could net you +10-15 points.
Other Things Worth Fixing
-
Missing reference files - Your references/README.md lists 5 files that don't exist. Either create them or remove the section. You're promising content you're not delivering.
-
Placeholder in Examples section - Line 128 just says "Example usage patterns will be demonstrated in context." That's not an example. Put in actual SQL - show a basic CREATE PROCEDURE, one with transactions, one with error handling.
-
Vague description - "Work with stored procedure generation" tells me nothing. Say what you actually do: "Generate stored procedures for PostgreSQL, MySQL, and SQL Server with security best practices."
-
No table of contents - Your file is 129 lines. Add a TOC after the frontmatter so people can jump to what they need.
Quick Wins
- Rewrite the 5 instruction steps to reference actual stored procedure concepts (parameters, transactions, return types)
- Create those missing reference files with database-specific syntax and patterns
- Add real SQL examples instead of placeholder text
- Update triggers to include database-specific phrases: "PostgreSQL stored procedure," "MySQL stored proc," "T-SQL procedure"
- Add a TOC for navigability
Focus on the big one first (making it actually useful) and the reference files - those two changes alone could swing your score to 50+.
Checkout your skill here: [SkillzWave.ai](https://skillzwave.ai) | [SpillWave](https://spillwave.com) We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.
I took a look at your generating-stored-procedures skill and wanted to share some thoughts.
Links:
The TL;DR
You're at 34/100, which puts you in F territory. This is based on Anthropic's 5-pillar rubric for skill quality. Your strongest area is Spec Compliance (14/15) - the frontmatter is solid. But you're getting crushed on Utility (3/20) and Progressive Disclosure (8/30). The core problem: this skill reads like a generic DevOps checklist, not a stored procedure expert.
What's Working Well
The Big One
Your skill is entirely generic. The 5-step workflow ("Assess Current State," "Review configuration") applies to literally any task. You promise PostgreSQL, MySQL, and SQL Server guidance in the description, but deliver absolutely nothing database-specific. Step 1 says "Review current configuration" - what configuration? There's no stored procedure context here.
The fix: Rewrite those 5 steps to be procedure-specific. Instead of "Assess Current State," do "Analyze Schema" - identify tables, define input parameters, document transaction requirements. Add actual CREATE PROCEDURE examples for each database. Create the reference files you're promising (postgresql_stored_procedure_best_practices.md, etc.). This alone could net you +10-15 points.
Other Things Worth Fixing
Missing reference files - Your references/README.md lists 5 files that don't exist. Either create them or remove the section. You're promising content you're not delivering.
Placeholder in Examples section - Line 128 just says "Example usage patterns will be demonstrated in context." That's not an example. Put in actual SQL - show a basic CREATE PROCEDURE, one with transactions, one with error handling.
Vague description - "Work with stored procedure generation" tells me nothing. Say what you actually do: "Generate stored procedures for PostgreSQL, MySQL, and SQL Server with security best practices."
No table of contents - Your file is 129 lines. Add a TOC after the frontmatter so people can jump to what they need.
Quick Wins
Focus on the big one first (making it actually useful) and the reference files - those two changes alone could swing your score to 50+.
Checkout your skill here: [SkillzWave.ai](https://skillzwave.ai) | [SpillWave](https://spillwave.com) We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.