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.

2.08x

Quality

70%

Does it follow best practices?

Impact

94%

2.08x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xdarkmatter/claude-mods/python-database-patterns/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

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

The body delivers lean, mostly-executable code examples across the core SQLAlchemy 2.0 topics, but it functions as an inlined reference catalog with no operation workflows/validation and references bundle files that are absent from the skill directory.

Suggestions

Create the referenced files under ./references/ and ./assets/ (or remove the references) so the Additional Resources links resolve.

For migrations and transactions, add a short validate-fix-retry loop (e.g. run `alembic upgrade` then check output before proceeding) to lift workflow clarity above the database cap of 3.

Tighten the FastAPI snippet so it is self-contained: define `app`, and import `HTTPException` and `select`, or note that imports carry over from earlier sections.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and lean — the one-line intro and sectioned examples avoid explaining concepts Claude already knows; the only redundancy is the Quick Reference table restating the Common Query Patterns section, keeping it just below level 5.	4 / 5
Actionability	Examples are concrete and copy-paste ready across models, async sessions, relationships, queries, and FastAPI integration, but minor gaps (undefined `User.age`/`role`/`created_at` fields, `@app.get` without an `app` definition, missing `HTTPException`/`select` imports in the FastAPI snippet) keep it from a 5.	4 / 5
Workflow Clarity	The content is a topical pattern catalog rather than a sequenced workflow, and database operations (migrations, transactions) appear without validation or validate-fix-retry feedback loops, which the rubric caps at 3 for database contexts.	3 / 5
Progressive Disclosure	Sectioning is clear and the "Additional Resources" section signals references with descriptions, but the referenced bundle files (./references/sqlalchemy-async.md, connection-pooling.md, transactions.md, migrations.md, ./assets/alembic.ini.template) do not exist on disk, so navigation is broken and substantial pattern content is inlined rather than split out.	3 / 5
	Total	14 / 20 Passed

Description

76%Weight 40%Scale 1-5

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 strong, explicit trigger guidance and a distinct niche, but its "what" statement is vague — it names the domain without enumerating concrete actions the skill performs.

Suggestions

Replace "database patterns for Python" with concrete actions, e.g. "Defines SQLAlchemy 2.0 models, async sessions, query patterns, and Alembic migrations for Python."

Lead with the capabilities before the trigger list so the "what" is as explicit as the "when".

Dimension	Reasoning	Score
Specificity	The phrase "SQLAlchemy and database patterns for Python" names the domain but lists no concrete actions — "patterns" is generic, matching the anchor that names the domain with minimal/generic actions rather than the level-3 anchor that requires 1-2 concrete actions.	2 / 5
Completeness	Both "what" (SQLAlchemy/database patterns for Python) and "when" (explicit "Triggers on:" clause) are present, with the trigger guidance being concrete and specific; it stays at 4 rather than 5 because the "what" lacks a list of concrete capabilities.	4 / 5
Trigger Term Quality	"Triggers on: sqlalchemy, database, orm, migration, alembic, async database, connection pool, repository pattern, unit of work" provides comprehensive coverage of natural terms users would say, including the library name, the migration tool, and common pattern synonyms.	5 / 5
Distinctiveness Conflict Risk	The SQLAlchemy/Alembic-specific triggers (alembic, sqlalchemy, connection pool, repository pattern, unit of work) carve out a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: NeverSight/skills_feed
Path: data/skills-md/0xdarkmatter/claude-mods/python-database-patterns/SKILL.md
Commit: 2f57aec

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.