sqlalchemy-starter

Scaffold a SQLAlchemy 2.0+ project with Python, declarative models (mapped_column), Alembic migrations, async sessions, repository pattern, relationships, and engine configuration.

Quality

81%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

79%

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

This is a high-quality, actionable skill with excellent code examples that are immediately usable. The content is appropriately concise and assumes Claude's competence. The main weaknesses are the lack of explicit validation steps for migration workflows and the monolithic structure that could benefit from progressive disclosure to separate reference files.

Suggestions

Add explicit validation checkpoints to the migration workflow, such as 'Verify migration: alembic current' after upgrade and guidance on what to do if migrations fail

Consider splitting detailed model patterns and repository examples into separate reference files (e.g., MODELS.md, REPOSITORIES.md) with the main skill providing a quick-start overview

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, providing only necessary code examples and configuration without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context.	3 / 3
Actionability	All code examples are fully executable and copy-paste ready, from the scaffold commands to complete model definitions, repository patterns, and Alembic configuration. Specific commands are provided for every operation.	3 / 3
Workflow Clarity	Steps are listed clearly (scaffold, init, migrate, etc.) but lacks explicit validation checkpoints. For database migrations which can be destructive, there's no feedback loop for verifying migration success or handling failures before proceeding.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but the skill is monolithic with all patterns inline. The Integration Notes mention other skills but the main content could benefit from splitting detailed patterns (models, repositories) into separate reference files.	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.

This is a strong description with excellent specificity and trigger term coverage for SQLAlchemy developers. The main weakness is the missing explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over other Python or database-related skills. The technical depth is appropriate for the target audience.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when setting up a new SQLAlchemy project, creating database models, configuring Alembic, or when the user mentions ORM setup or database scaffolding.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Scaffold a SQLAlchemy 2.0+ project' with detailed components including 'declarative models (mapped_column)', 'Alembic migrations', 'async sessions', 'repository pattern', 'relationships', and 'engine configuration'.	3 / 3
Completeness	Clearly answers 'what does this do' (scaffold SQLAlchemy projects with specific components), but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill.	2 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'SQLAlchemy', 'Python', 'Alembic', 'migrations', 'async sessions', 'repository pattern', 'mapped_column', 'relationships', 'engine configuration'. These are terms developers naturally use when working with SQLAlchemy projects.	3 / 3
Distinctiveness Conflict Risk	Very specific niche targeting SQLAlchemy 2.0+ with particular patterns (repository pattern, Alembic, async sessions). Unlikely to conflict with generic Python or database skills due to the specific technology stack and version mentioned.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 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: achreftlili/deep-dev-skills
Commit: 181fcbc

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