generating-stored-procedures
This skill uses the stored-procedure-generator plugin to create production-ready stored procedures, functions, triggers, and custom database logic. It supports PostgreSQL, MySQL, and SQL Server. Use this skill when the user asks to "generate stored procedure", "create database function", "write a trigger", or needs help with "database logic", "optimizing database performance", or "ensuring transaction safety" in their database. The skill is activated by requests related to database stored procedures, functions, or triggers.
68
53%
Does it follow best practices?
Impact
100%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-batch-20251204-000554/plugins/database/stored-procedure-generator/skills/stored-procedure-generator/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 strong description that clearly communicates what the skill does, which databases it supports, and when it should be activated. It includes explicit trigger terms in natural language and has a well-defined niche. The only minor weakness is slight redundancy in the last sentence which restates what was already covered.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create production-ready stored procedures, functions, triggers, and custom database logic' and specifies supported databases (PostgreSQL, MySQL, SQL Server). | 3 / 3 |
Completeness | Clearly answers both 'what' (creates stored procedures, functions, triggers, custom database logic for PostgreSQL/MySQL/SQL Server) and 'when' (explicit 'Use this skill when...' clause with multiple trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'generate stored procedure', 'create database function', 'write a trigger', 'database logic', 'optimizing database performance', 'ensuring transaction safety'. Good coverage of natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to stored procedures, functions, triggers, and database logic with specific database engine mentions. Unlikely to conflict with general SQL query skills or other database skills due to the narrow focus on procedural database objects. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is almost entirely descriptive and abstract, providing no executable SQL code, no concrete templates, and no actionable guidance. It reads like a marketing description of what the skill does rather than instructions that would help Claude actually generate stored procedures. The content explains obvious concepts Claude already knows while failing to provide the specific patterns, syntax examples, and validation steps that would make it useful.
Suggestions
Replace the abstract examples with actual executable SQL code showing complete stored procedure, function, and trigger templates for each supported database (PostgreSQL, MySQL, SQL Server).
Add validation and testing steps to the workflow, such as syntax checking, test execution with sample data, and rollback procedures for failed deployments.
Remove the 'Overview', 'When to Use', and 'How It Works' sections which explain concepts Claude already knows, and replace them with concrete patterns, common pitfalls, and database-specific syntax differences.
Include specific guidance on how to invoke the stored-procedure-generator plugin, including any required parameters, configuration options, or API calls.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what stored procedures are, why to use them, what triggers do). The 'Overview', 'When to Use', and 'How It Works' sections are padded with obvious information that adds no actionable value. The examples describe what the skill will do in abstract terms rather than showing actual code. | 1 / 3 |
Actionability | There is zero executable code, no concrete SQL examples, no specific commands, and no actual stored procedure templates. The examples merely describe a hypothetical workflow ('The skill will: 1. Analyze the request...') without showing any actual generated SQL output. This is entirely descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | The 'How It Works' section is a vague three-step process (identify, generate, present) with no validation checkpoints, no error handling, and no feedback loops. There's no guidance on testing generated procedures, validating SQL syntax, or handling failures during deployment. | 1 / 3 |
Progressive Disclosure | The content has some structural organization with clear section headers, but it's a monolithic file with no references to supporting files. The content that exists is mostly filler that could be replaced with actual templates or examples, and there are no bundle files to reference. | 2 / 3 |
Total | 5 / 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
9be4627
- 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.