python-database-patterns
SQLAlchemy and database patterns for Python. Triggers on: sqlalchemy, database, orm, migration, alembic, async database, connection pool, repository pattern, unit of work.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill python-database-patterns83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%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 description has strong trigger term coverage and clear distinctiveness for Python database work, but lacks specificity about what concrete actions the skill enables. The 'Triggers on:' format effectively communicates when to use it, but the capability description is too brief to help Claude understand what the skill actually does.
Suggestions
Add specific actions the skill enables, e.g., 'Define SQLAlchemy models, write database queries, configure connection pools, create Alembic migrations'
Expand the opening to describe concrete capabilities before the trigger list, e.g., 'Implements database models, queries, and migrations using SQLAlchemy ORM patterns'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SQLAlchemy, database patterns) and mentions some concepts (orm, migration, connection pool, repository pattern), but doesn't list concrete actions like 'create models', 'write queries', or 'configure connections'. | 2 / 3 |
Completeness | The 'Triggers on:' clause provides explicit trigger guidance (satisfying 'when'), but the 'what' portion is weak - it only says 'SQLAlchemy and database patterns' without explaining what actions or capabilities the skill provides. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'sqlalchemy', 'database', 'orm', 'migration', 'alembic', 'async database', 'connection pool', 'repository pattern', 'unit of work' - these are all terms developers naturally use when working with Python databases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Python-specific database terms like 'sqlalchemy', 'alembic', 'repository pattern', and 'unit of work' that clearly differentiate it from generic database skills or other language-specific database tools. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently covers SQLAlchemy 2.0 patterns with executable, copy-paste ready code. The progressive disclosure is excellent with clear references to deeper topics. The main weakness is the lack of explicit workflow guidance for multi-step operations like migrations or schema changes, which could benefit from validation checkpoints.
Suggestions
Add a brief workflow section for database setup/migration with explicit validation steps (e.g., 'Run alembic check before applying migrations')
Include error handling patterns or common pitfalls section for database operations that can fail silently
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, jumping directly into executable code examples without explaining what SQLAlchemy or databases are. Every section provides concrete patterns without unnecessary preamble. | 3 / 3 |
Actionability | All code examples are fully executable with proper imports, complete class definitions, and copy-paste ready patterns. The quick reference table provides immediate lookup for common operations. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit workflow for database setup, migration, or validation steps. For operations like schema changes or migrations, there are no validation checkpoints or error recovery guidance. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview of core patterns in the main file, then clear one-level-deep references to detailed topics (async, pooling, transactions, migrations) in separate files. Navigation is well-signaled. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 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.