atlas-best-practices

Patterns for Atlas database schema management covering HCL/SQL schema definitions, versioned and declarative migrations, linting analyzers, testing, and project configuration. Use when working with atlas.hcl, .hcl schema files, Atlas CLI commands, or database migrations.

1.10x

Quality

80%

Does it follow best practices?

Impact

97%

1.10x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xbigboss/claude-code/atlas-best-practices/SKILL.md

Quality

Content

72%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.

Highly actionable reference content packed with executable Atlas examples, but it is structured as a flat topic catalog rather than checkpointed migration workflows, and the large inlined body has no progressive disclosure via bundle files.

Suggestions

Add an explicit ordered production-migration workflow with validation checkpoints (e.g. atlas migrate lint → atlas migrate validate → fix → atlas migrate apply) to lift workflow_clarity above the destructive-ops cap of 3.

Move large reference blocks (full HCL schema examples, ORM integration, CI/CD, the command catalog) into separate files under references/ and link to them from SKILL.md to improve progressive disclosure.

Trim the closing "Instructions" section since its bullets duplicate guidance already given in the Dev Database, Migration Linting, and workflow sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, executable code with terse prose and only a brief justified intro (Atlas is a specific tool), but the closing "Instructions" section reiterates guidance already covered in earlier sections and could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready bash commands, HCL config, SQL DDL, test files, and CI YAML covering the common Atlas cases, matching the fully-executable 5 anchor.	5 / 5
Workflow Clarity	The body is organized as a topic reference rather than a sequenced workflow, and for destructive/batch database migrations it lacks an explicit validate→fix→retry feedback loop; lint and validate commands exist as separate entries but are not woven into checkpointed steps, so the destructive-ops cap of 3 applies.	3 / 5
Progressive Disclosure	No bundle files exist and all content (full schema examples, ORM integration, CI/CD, command catalog) is inlined in a ~340-line body; section headers give structure, but material that belongs in separate reference files is not split out and there are no external references.	3 / 5
	Total	15 / 20 Passed

Description

87%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.

A strong, third-person description that clearly states both what it covers and when to use it, with Atlas-specific trigger terms and file extensions. Slight room to convert topic nouns into concrete actions for maximum specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete coverage areas ("HCL/SQL schema definitions, versioned and declarative migrations, linting analyzers, testing, and project configuration"), but these are topic nouns rather than concrete verb-driven actions like the 5-anchor examples, leaving minor gaps.	4 / 5
Completeness	It explicitly states what ("Patterns for Atlas database schema management covering...") and when ("Use when working with atlas.hcl, .hcl schema files, Atlas CLI commands, or database migrations") with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	"Use when working with atlas.hcl, .hcl schema files, Atlas CLI commands, or database migrations" provides good natural keyword coverage including a file extension, though a few synonyms (e.g. "schema migrations") are missing.	4 / 5
Distinctiveness Conflict Risk	The Atlas-specific niche with distinct triggers (atlas.hcl, Atlas CLI) gives it a clear scope with minimal overlap risk against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Path: data/skills-md/0xbigboss/claude-code/atlas-best-practices/SKILL.md
Commit: 2f57aec

Reviewed: about 22 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.