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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-stored-procedures91
Quality
86%
Does it follow best practices?
Impact
96%
0.98xAverage score across 6 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/database/stored-procedure-generator/skills/generating-stored-procedures/SKILL.mdDiscovery
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 capabilities (stored procedures, functions, triggers with error handling), names supported database systems, and provides explicit trigger guidance with natural user phrases. 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, or deploy stored procedures', 'Creates database functions, triggers, and procedures with proper error handling and transaction management'. Covers specific database systems (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 plus 'Trigger with phrases like' section providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would say: 'generate stored procedure', 'create database function', 'write SQL procedure', 'add trigger to table', 'create CRUD procedures'. These are realistic user requests. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on stored procedures, database functions, and triggers for specific database systems. The trigger phrases are highly specific to this domain and unlikely to conflict with general SQL query skills or other database tools. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent executable examples across three database platforms and good structural organization. The main weaknesses are some verbosity in showing similar patterns three times and missing explicit validation/verification steps in the deployment workflow for what are potentially destructive database operations.
Suggestions
Add explicit validation checkpoint after deployment (e.g., 'Verify procedure exists: SELECT routine_name FROM information_schema.routines') before considering the task complete
Consider consolidating the three database examples into a pattern table showing syntax differences, with one full example, to reduce token usage
Add a rollback verification step to confirm the rollback script works before deploying to production environments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - showing nearly identical patterns across three database types when the differences could be summarized more concisely. The examples are useful but verbose for what Claude already knows about SQL syntax. | 2 / 3 |
Actionability | Provides fully executable SQL code for all three database types with complete, copy-paste ready examples. Includes concrete CLI commands for validation and deployment scripts with specific parameters. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered (1-5) with a logical sequence, but lacks explicit validation checkpoints between steps. For database operations that could be destructive, there's no feedback loop for verifying deployment success before proceeding or rollback verification. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections (Prerequisites, Instructions, Output, Error Handling, Examples, Resources). References to external files are one level deep and clearly signaled. The main content stays focused while pointing to detailed best practices documents. | 3 / 3 |
Total | 10 / 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 | |
- 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.