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".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 for three major database platforms), lists concrete actions (generate, validate, deploy), and provides explicit trigger phrases that users would naturally use. The description is concise yet comprehensive, making it easy for Claude to select this skill appropriately.
| 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. Also specifies three database platforms (PostgreSQL, MySQL, SQL Server). | 3 / 3 |
Completeness | Clearly answers both 'what' (creates database functions, triggers, procedures with error handling and transaction management) and 'when' (explicit 'Use when' clause at the start plus 'Trigger with phrases like...' providing specific trigger guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'generate stored procedure', 'create database function', 'write SQL procedure', 'add trigger to table', 'create CRUD procedures'. These are phrases users would naturally say, and the description also includes keywords like PostgreSQL, MySQL, SQL Server. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on stored procedures, database functions, and triggers for specific database 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
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, executable SQL examples across three database platforms with good error handling patterns and a clear deployment workflow. Its main weaknesses are the inline verbosity from triplicating every example across all three databases (which could be split into referenced files), a missing validation feedback loop after deployment, and some redundant content like the duplicated Overview section at the bottom.
Suggestions
Add an explicit feedback loop after Step 5 (Deploy): verify the procedure was created successfully (e.g., query information_schema), and specify rollback steps if deployment fails.
Move the full database-specific examples into separate referenced files (e.g., postgresql_examples.md, mysql_examples.md) and keep only one representative example inline to reduce token usage.
Remove the redundant 'Overview' section at the bottom, which duplicates the skill description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary content. The Prerequisites section explains obvious things, the Examples section shows conversation snippets rather than executable code, and the Overview at the bottom is redundant with the title/description. The three parallel database examples add bulk but are justified given the multi-database scope. | 2 / 3 |
Actionability | The skill provides fully executable SQL code for all three database types, concrete bash commands for validation and deployment, and specific error handling patterns. The code examples are copy-paste ready with proper syntax for each database dialect. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (identify → generate → add transactions → validate → deploy), but there's no explicit feedback loop after deployment validation. The validate step references a script but doesn't specify what to do if validation fails beyond 'use database-specific syntax validator' in the error table. Missing explicit verify-after-deploy checkpoint. | 2 / 3 |
Progressive Disclosure | The Resources section properly references external files for best practices and optimization, which is good progressive disclosure. However, the main content is quite long with three full database examples inline that could be split into separate reference files per database type, with only one example kept inline as a representative pattern. | 2 / 3 |
Total | 9 / 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
c8a915c
- 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.