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".

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/database/stored-procedure-generator/skills/generating-stored-procedures/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concrete and well-stocked with executable multi-dialect examples and a useful error table, but it has actionable gaps: fragile '#' comments in MySQL examples, missing SQL Server validate/deploy coverage, no explicit validate-before-deploy gate, and advertised assets that are absent. Tightening these would lift the weaker dimensions.

Suggestions

Replace the '#' line comments inside the MySQL SIGNAL statements with '-- ' comments (or remove them) so the examples are idiomatic and unambiguous, and add the missing SQL Server validate/deploy command examples to Step 4 and Step 5.

Make validation an explicit gate in the workflow: after Step 4, state 'fix any reported errors and re-run the validator; only proceed to deploy once validation passes', turning the sequence into a validate -> fix -> retry feedback loop.

Either add the advertised stored_procedure_template.sql and example_stored_procedures/ assets or remove them from assets/README.md, and signal the reference docs inline at the relevant steps (e.g., link the per-engine best-practices file next to its code block).

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete code with no basic-concept padding, but it is lengthy and includes a redundant trailing '## Overview' that restates the description's 'Use when' sentence; it could be tightened. Not score 3 because it is not maximally lean, and not score 1 because there is no conceptual fluff.	2 / 3
Actionability	Provides concrete executable SQL in three dialects and real script invocations, but the MySQL examples use '#' line comments mid-statement ('SIGNAL SQLSTATE \'45000\' # 45000 = configured value'), and the Step 4/5 validate-and-deploy examples omit SQL Server despite the skill supporting it. These are incomplete key details per the score-2 anchor rather than fully copy-paste ready.	2 / 3
Workflow Clarity	The five steps are clearly sequenced and a validation step exists, but deploying stored procedures to a database is a destructive operation and the workflow never frames validation as a gate ('fix and re-validate; only deploy when valid'). Per the rubric's database-operation feedback-loop rule, workflow clarity is capped at 2.	2 / 3
Progressive Disclosure	References are organized one level deep in a Resources section and all referenced reference/script files exist, but they are listed at the end rather than signaled inline at the relevant steps, and assets/README advertises a stored_procedure_template.sql and example_stored_procedures/ directory that do not exist and are never referenced. This is some structure with organization gaps per the score-2 anchor.	2 / 3
	Total	8 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, concrete multi-action capabilities, explicit 'Use when' trigger guidance, and natural trigger phrases. It clearly communicates both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('generate, validate, or deploy stored procedures', 'Creates database functions, triggers, and procedures with proper error handling and transaction management') across three named engines, matching the score-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('generate, validate, or deploy stored procedures... Creates database functions, triggers, and procedures') and when ('Use when you need to generate, validate, or deploy stored procedures') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would actually say ('generate stored procedure', 'create database function', 'write SQL procedure', 'add trigger to table', 'create CRUD procedures'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The stored-procedure niche scoped to PostgreSQL, MySQL, and SQL Server with distinct trigger phrases is unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/database/stored-procedure-generator/skills/generating-stored-procedures/SKILL.md
Commit: be8dd2e

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.