elixir-antipatterns

Core catalog of 8 critical Elixir/Phoenix anti-patterns covering error handling, separation of concerns, Ecto queries, and testing. Trigger: During Elixir code review, refactoring sessions, or when writing Phoenix/Ecto code.

Quality

75%

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 ./community/elixir-antipatterns/SKILL.md

Quality

Content

63%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 highly actionable with executable paired BAD/GOOD examples and clear organization, but it is held back by significant code duplication across sections and a broken reference path to the extended bundle file.

Suggestions

Remove the duplicate code blocks: keep each pattern's BAD/GOOD example in only one place (e.g. the Anti-Patterns section) and have the Code Examples section reference them or show distinct cases.

Fix the extended reference path so it points to the actual bundle file, e.g. 'See assets/extended.md' instead of 'EXTENDED.md'.

Consider dropping the redundant Quick Reference table or trimming it to only the patterns not already shown in full above.

Dimension	Reasoning	Score
Conciseness	Three patterns (tagged tuples, LiveView context separation, N+1 queries) appear as full duplicated BAD/GOOD code blocks in both 'Code Examples' and 'Anti-Patterns', and the Quick Reference table repeats all eight again, creating several padded sections.	2 / 5
Actionability	Concrete, copy-paste-ready Elixir code with @spec, real Repo/Ecto calls, and paired BAD/GOOD examples covers the common cases fully.	5 / 5
Workflow Clarity	As a pattern catalog rather than a destructive workflow, it is well organized with 'When to Use' and a Quick Reference table for application guidance; no multi-step validation sequence is needed, so it sits just below the top anchor.	4 / 5
Progressive Disclosure	Structure and one-level signaling are good, but the body repeatedly references 'EXTENDED.md' while the actual bundle file is 'assets/extended.md', so the referenced path does not resolve to the real file.	3 / 5
	Total	14 / 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.

The description clearly states both what the skill covers and when to use it, with concrete trigger scenarios and a distinct Elixir/Phoenix niche. It is slightly more a coverage-area list than a discrete-action list, which keeps specificity just below the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and four concrete coverage areas (error handling, separation of concerns, Ecto queries, testing) plus a pattern count, but describes covered topics rather than discrete actions, placing it between anchors 4 and 5.	4 / 5
Completeness	Explicitly answers both what ('Core catalog of 8 critical Elixir/Phoenix anti-patterns...') and when ('Trigger: During Elixir code review, refactoring sessions, or when writing Phoenix/Ecto code') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'Elixir code review', 'refactoring sessions', and 'writing Phoenix/Ecto code' give good keyword coverage, though synonyms like BEAM/Erlang are absent.	4 / 5
Distinctiveness Conflict Risk	The Elixir/Phoenix niche with framework-specific triggers (Ecto, LiveView, ExUnit) is distinct and unlikely to fire for unrelated 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: Gentleman-Programming/Gentleman-Skills
Path: community/elixir-antipatterns/SKILL.md
Commit: c8036a3

Reviewed: 5 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.