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

—

Does it follow best practices?

Impact

94%

2.08x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

80%

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

The body is a concise, actionable SQLAlchemy 2.0 reference with executable examples. Its main weaknesses are the absence of validation/feedback checkpoints for risky database operations and a set of referenced bundle files that do not actually exist.

Suggestions

Add explicit validation/rollback checkpoints for destructive operations, e.g. "Back up the database and test Alembic migrations against a copy before applying," and a verify step after schema changes.

Create the referenced bundle files (sqlalchemy-async.md, connection-pooling.md, transactions.md, migrations.md, alembic.ini.template) or remove the broken references so progressive disclosure is navigable.

Make examples fully copy-paste runnable by adding missing imports/definitions (String, HTTPException, app, AsyncGenerator).

Dimension	Reasoning	Score
Conciseness	The body is code-forward and lean: a one-line intro, executable snippets with brief comments, and a compact Quick Reference table, with no padding explaining concepts Claude already knows.	3 / 3
Actionability	It provides real, executable SQLAlchemy 2.0 code (models, async engine, relationships, query patterns, FastAPI integration) rather than pseudocode, matching the copy-paste-ready anchor.	3 / 3
Workflow Clarity	Content is organized by topic but there is no sequenced multi-step workflow, and risky database operations (migrations, schema changes, transactions) lack any validate/verify or rollback checkpoint, which caps the score per the database feedback-loop guidance.	2 / 3
Progressive Disclosure	The Additional Resources and Assets sections are well-signaled and one level deep, but every referenced file (./references/*.md, ./assets/alembic.ini.template) is missing, so navigation is broken and the disclosure is incomplete.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 is strong on trigger coverage and answers both what and when explicitly. It is held back by an abstract "patterns" framing and some overlap with sibling async/fastapi skills.

Suggestions

Replace the abstract "database patterns" framing with concrete actions, e.g. "Define SQLAlchemy 2.0 models, run Alembic migrations, configure connection pools, and manage async sessions."

Disambiguate overlapping triggers: clarify that "async database" here means async SQLAlchemy sessions specifically, to reduce conflict with python-async-patterns.

Dimension	Reasoning	Score
Specificity	Names the domain and some action-adjacent terms ("SQLAlchemy and database patterns for Python", "migration", "connection pool"), but the "what" portion uses the abstract word "patterns" rather than enumerating multiple concrete actions, so it does not reach the multi-action anchor.	2 / 3
Completeness	It states what the skill does ("SQLAlchemy and database patterns for Python") and gives explicit when-guidance via the "Triggers on:" clause, which is an equivalent explicit trigger clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	The explicit "Triggers on: sqlalchemy, database, orm, migration, alembic, async database, connection pool, repository pattern, unit of work" gives good coverage of natural terms a user would actually say, matching the high-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	SQLAlchemy is a fairly specific niche, but the generic term "database" and "async database" overlap with declared sibling skills (python-async-patterns, python-fastapi-patterns), so it could still trigger for the wrong skill.	2 / 3
	Total	10 / 12 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
Commit: 26d37ce

Reviewed: 4 days 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.