generating-stored-procedures
Use when you need to generate, validate, or deploy stored procedures for PostgreSQL, MySQL, or SQL Server. Creates database functions, triggers, and procedures with proper error handling and transaction management. Trigger with phrases like "generate stored procedure", "create database function", "write SQL procedure", "add trigger to table", or "create CRUD procedures".
72
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/database/stored-procedure-generator/skills/generating-stored-procedures/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly specifies the domain (stored procedures, functions, triggers), the supported platforms (PostgreSQL, MySQL, SQL Server), concrete capabilities (generate, validate, deploy with error handling and transaction management), and provides explicit trigger phrases users would naturally use. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generate, validate, deploy stored procedures; creates database functions, triggers, and procedures; mentions proper error handling and transaction management across three specific database platforms. | 3 / 3 |
Completeness | Clearly answers both 'what' (generates, validates, deploys stored procedures, functions, triggers with error handling and transaction management) and 'when' (explicit 'Use when' clause and 'Trigger with phrases like' providing concrete trigger guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'generate stored procedure', 'create database function', 'write SQL procedure', 'add trigger to table', 'create CRUD procedures', plus database names PostgreSQL, MySQL, SQL Server. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on stored procedures, database functions, and triggers for specific RDBMS platforms. Unlikely to conflict with general SQL query skills or other database skills due to the specific focus on procedural database objects. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is overly verbose, repeating nearly identical patterns across three database dialects where a single example with dialect notes would suffice. It references multiple scripts and reference files that don't exist in the bundle, undermining both actionability and progressive disclosure. The workflow is reasonably structured but lacks verification steps after deployment and relies on phantom tooling.
Suggestions
Consolidate the three-dialect examples into one primary dialect with a concise comparison table for syntax differences, cutting the body length by ~50%.
Either include the referenced scripts (stored_procedure_syntax_validator.py, stored_procedure_deployer.py) in the bundle or replace Steps 4-5 with direct database CLI commands (psql, mysql, sqlcmd) that are immediately executable.
Add an explicit verification step after deployment (e.g., 'Call the procedure with test data and confirm expected output') to close the feedback loop.
Remove the redundant 'Overview' section at the bottom and the 'Prerequisites' section that explains obvious requirements Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines, showing nearly identical patterns across three database types for both simple queries and transactions. Claude already knows SQL syntax for PostgreSQL, MySQL, and SQL Server. The three-way repetition of get-user-by-id and transfer-funds patterns is highly redundant and could be condensed to a single example with a note about dialect differences. | 1 / 3 |
Actionability | The SQL code examples are concrete and mostly executable, which is good. However, the skill references scripts (stored_procedure_syntax_validator.py, stored_procedure_deployer.py) that don't exist in the bundle, making Steps 4 and 5 non-actionable. The 'Examples' section shows conversation snippets rather than actual executable output, reducing actionability. | 2 / 3 |
Workflow Clarity | The five steps provide a clear sequence from identification through deployment. However, there's no explicit validation checkpoint between deployment and confirmation—no 'verify the procedure works by calling it' step. The validate step references a non-existent script, and there's no feedback loop for deployment failures beyond the error table. | 2 / 3 |
Progressive Disclosure | The skill references five external files in the Resources section, which is good structure. However, none of these files exist in the bundle, making the references hollow. The main body contains extensive inline code that could be split into per-database reference files, and the redundant Overview section at the bottom suggests poor organization. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.