Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

elixir-ecto

Ecto schemas, changesets, queries, migrations, and database patterns for Elixir applications

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skill/elixir-ecto/SKILL.md

Quality

Content

57%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 is a comprehensive, actionable Ecto reference with strong executable examples and clear section structure, but it suffers from being a monolithic ~900-line SKILL.md with no reference files and from missing validation checkpoints in its destructive migration workflows. Splitting advanced catalogs into reference files and adding verification steps would substantially improve the score.

Suggestions

Move the large query and migration pattern catalogs into reference files (e.g. references/queries.md, references/migrations.md) and keep SKILL.md as a concise overview, improving both conciseness and progressive_disclosure.

Add explicit validation checkpoints to destructive/batch migration workflows (e.g. 'verify all rows backfilled and non-null before adding NOT NULL constraint') to lift the workflow_clarity cap.

Fix the apparent Enum.max(Date, fn -> nil end) bug and ensure all referenced modules (Comment, Post, Tag) are aliased so examples are copy-paste executable.

Dimension	Reasoning	Score
Conciseness	Prose is lean and mostly code with little padding, but the entire ~900-line body is inlined in SKILL.md where much could be split into reference files, so it is mostly efficient but could be tightened and reorganized.	3 / 5
Actionability	Extensive copy-paste-ready Elixir examples cover common cases across schemas, changesets, queries, and migrations, but some modules are referenced without aliases and there is an apparent bug (Enum.max(Date, ...) at line 501), leaving minor gaps below the fully-executable anchor 5.	4 / 5
Workflow Clarity	The zero-downtime and data-migration sections are sequenced, but destructive/batch operations (migrations, update_all backfills) lack explicit validation/verification checkpoints, which per the guidelines caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	Sections are well-organized and cross-references to sibling skills are clear, but no bundle files exist and content that belongs in separate reference files (e.g. the full query and migration catalogs) is fully inlined, matching the 'structure present but content that should be separate is inline' anchor.	3 / 5
	Total	13 / 20 Passed

Description

66%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 is specific and rich in natural Ecto trigger terms, but it omits any explicit "Use when..." guidance, so it answers "what" well without answering "when". This caps completeness despite otherwise strong specificity and distinctiveness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when working with Ecto schemas, changesets, queries, or migrations in Elixir applications' to satisfy the completeness dimension.

Replace the generic 'database patterns' with one or two more concrete capabilities to push specificity toward the top anchor.

Mention 'Repo' or 'Elixir database layer' as additional natural trigger terms users are likely to say.

Dimension	Reasoning	Score
Specificity	Lists several concrete Ecto capabilities ("schemas, changesets, queries, migrations") matching the 'lists several specific actions; minor gaps' anchor, but "database patterns" keeps it just below the comprehensive anchor 5.	4 / 5
Completeness	The description gives a clear "what" but has no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	"Ecto", "schemas", "changesets", "queries", "migrations", and "Elixir" are natural terms a developer would say, giving good keyword coverage; a few natural variants (e.g. "Repo", "Elixir database") are absent.	4 / 5
Distinctiveness Conflict Risk	Ecto is a distinct niche with clear triggers, but it overlaps with sibling Elixir skills (Phoenix, architecture, review) referenced in the body, giving minor overlap risk rather than minimal.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (903 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: vircung/opencode-config
Path: skill/elixir-ecto/SKILL.md
Revision: e2b74bf

Reviewed: 24 days ago

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.

elixir-ecto

Table of Contents

Is this your skill?