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.
74
63%
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
54%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 with specific technologies and patterns listed, but it severely lacks specificity about what concrete actions the skill performs. The 'what' portion is essentially just a topic label ('SQLAlchemy and database patterns') rather than a description of capabilities. Adding concrete actions would significantly improve this description.
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 as a 'Use when...' clause with context, e.g., 'Use when the user needs to set up or modify SQLAlchemy models, write database migrations with Alembic, or implement async database access patterns.'
| 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. The trigger list partially compensates but there's no explicit 'Use when...' guidance with context. | 2 / 3 |
Trigger Term Quality | 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 mention of SQLAlchemy and Alembic specifically helps distinguish it, but 'database' and 'orm' are generic enough to potentially overlap with other database-related skills (e.g., raw SQL, Django ORM, or general database administration skills). | 2 / 3 |
Total | 8 / 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 project setup order and error handling/validation checkpoints.
Suggestions
Trim the Common Query Patterns section — basic AND/OR/ORDER BY/LIMIT patterns are well-known to Claude; focus on SQLAlchemy-specific gotchas instead.
Add a brief workflow section showing the recommended setup sequence (engine config → define models → run migrations → query) with validation checkpoints like testing the connection before proceeding.
Include error handling patterns for common database failures (connection errors, integrity constraint violations, deadlocks) since these are where real-world usage breaks down.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some patterns Claude already knows well (basic ORM relationships, simple query patterns like AND/OR conditions). 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 complete with proper imports. | 3 / 3 |
Workflow Clarity | The skill presents individual patterns well but lacks workflow sequencing — there's no guidance on the order of operations for setting up a project (engine → models → migrations → queries), no validation steps for database operations, and no error handling patterns for common failures like connection issues or constraint violations. | 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 aids 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
f772de4
- 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.