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.
77
67%
Does it follow best practices?
Impact
94%
2.08xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/python-database-patterns/SKILL.mdQuality
Discovery
62%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 has excellent trigger term coverage and clear distinctiveness within the Python/SQLAlchemy domain, but it critically lacks specificity about what concrete actions the skill enables. Adding explicit capabilities (e.g., 'define models', 'configure connection pools', 'create Alembic migrations') and a proper 'Use when...' clause would significantly improve it.
Suggestions
Add specific concrete actions the skill covers, e.g., 'Defines SQLAlchemy models, configures connection pools, creates Alembic migrations, implements repository and unit of work patterns.'
Reframe the trigger list into a 'Use when...' clause, e.g., 'Use when the user needs help with SQLAlchemy ORM setup, database migrations with Alembic, async database connections, or repository/unit of work patterns in Python.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'SQLAlchemy and database patterns for Python' which names the domain but lists no concrete actions. There are no specific capabilities like 'create models', 'run migrations', 'configure connection pools', etc. | 1 / 3 |
Completeness | The 'when' is partially addressed via the 'Triggers on:' clause listing keywords, but the 'what' is extremely weak — it only says 'database patterns' without describing what the skill actually does. There is no explicit 'Use when...' clause, but the 'Triggers on:' serves a similar function, so it narrowly avoids a 1. | 2 / 3 |
Trigger Term Quality | The description includes a strong set of natural trigger terms: 'sqlalchemy', 'database', 'orm', 'migration', 'alembic', 'async database', 'connection pool', 'repository pattern', 'unit of work'. These cover common variations a user would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of SQLAlchemy, Alembic, repository pattern, and unit of work creates a clear niche focused on Python ORM/database patterns. This is unlikely to conflict with generic database or other language-specific skills. | 3 / 3 |
Total | 9 / 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 reference skill with excellent actionability and progressive disclosure. The code examples are concrete and use modern SQLAlchemy 2.0 patterns consistently. However, it could be more concise by trimming basic query patterns Claude already knows, and would benefit from workflow guidance around migrations and transaction management with validation steps.
Suggestions
Trim the Common Query Patterns section significantly - basic select, where, order_by, and join are well-known SQLAlchemy patterns that don't need full examples
Add a brief workflow section for database setup/migration with validation checkpoints (e.g., test connection → run migrations → verify schema)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some patterns Claude already knows well (basic ORM relationships, simple query patterns). The quick reference table and common query patterns section could be trimmed since these are well-documented SQLAlchemy basics. | 2 / 3 |
Actionability | All code examples are fully executable, copy-paste ready, and use SQLAlchemy 2.0 style consistently. The FastAPI integration, async patterns, and model definitions are concrete and specific with real import statements and complete snippets. | 3 / 3 |
Workflow Clarity | The skill presents individual patterns well but lacks workflow sequencing - there's no guidance on the order of operations (e.g., create engine → define models → create tables → run queries), no validation checkpoints for migrations, and no error handling patterns for database operations that could fail. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview of core patterns inline, then well-signaled one-level-deep references to async patterns, connection pooling, transactions, and migrations. The See Also section with prerequisites and related skills provides good navigation. | 3 / 3 |
Total | 10 / 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 | |
- Repository
- NeverSight/skills_feed
- Commit
9f4534c
- 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.