CtrlK
BlogDocsLog inGet started
Tessl Logo

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

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is highly actionable with executable multi-dialect SQL and real supporting scripts, and it uses clean one-level-deep references. Its main gaps are a missing validate-fix-retry feedback loop for database operations and some redundancy (a duplicate Overview section and parallel dialect examples) that could be tightened.

Suggestions

Add an explicit feedback loop to Step 4/5: 'If validation reports errors, fix the SQL and re-run the validator before deploying' to satisfy the database-operation validation requirement.

Remove the trailing '## Overview' section, which merely restates the frontmatter description and adds redundant tokens.

Consider moving the full per-dialect code templates into the existing references and keeping one canonical example inline to reduce token weight from near-parallel SQL blocks.

DimensionReasoningScore

Conciseness

The body is mostly efficient with terse prerequisites, an error table, and direct code, but could be tightened: a trailing '## Overview' restates the frontmatter description and the near-parallel full code blocks for all three dialects add tokens beyond the minimum.

2 / 3

Actionability

Provides fully executable SQL for PostgreSQL, MySQL, and SQL Server plus concrete validator/deployer command lines with real ${CLAUDE_SKILL_DIR} script paths that exist in the bundle, making it copy-paste ready.

3 / 3

Workflow Clarity

The 5-step sequence (identify → generate → transaction → validate → deploy) is clearly ordered and includes a validation step, but it lacks an explicit validate→fix→retry feedback loop, which the rubric requires for database/destructive operations.

2 / 3

Progressive Disclosure

The body offers a clear overview with well-signaled one-level-deep references to real reference files (per-dialect best practices, security, optimization) and scripts, all of which exist in the bundle, with easy navigation.

3 / 3

Total

10

/

12

Passed

Description

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.

The description is specific, well-scoped to three named databases, and pairs concrete capabilities with explicit natural-language trigger phrases. It cleanly answers both 'what' and 'when' without padding.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'generate, validate, or deploy stored procedures' and 'Creates database functions, triggers, and procedures with proper error handling and transaction management' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Clearly answers both what (creates functions/triggers/procedures with error handling and transaction management) and when ('Use when you need to generate, validate, or deploy stored procedures...') with explicit triggers, matching the top anchor.

3 / 3

Trigger Term Quality

Provides five 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 natural terms.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — stored procedures for PostgreSQL, MySQL, or SQL Server — with distinct, specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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