Name: elixir-pro
Rating: 48 (1 reviews)
Author: administrakt0r

elixir-pro

Write idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView. Masters concurrency, fault tolerance, and distributed systems.

Quality

51%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/elixir-pro/SKILL.md

The canonical home for this skill is elixir-pro in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

36%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 well-structured but generic and lacks executable Elixir guidance, with a dangling reference to a missing playbook file. Concrete code examples and either creating or removing the referenced file would substantially improve it.

Suggestions

Add at least one copy-paste-ready Elixir code example (e.g., a supervised GenServer or LiveView snippet) to make guidance executable.

Replace the vague "Instructions" bullets with a concrete sequenced workflow with validation checkpoints (e.g., run `mix test`, `mix credo`, `dialyzer` before finishing).

Resolve the broken reference: either create resources/implementation-playbook.md or remove the pointer to it so navigation is not misleading.

Dimension	Reasoning	Score
Conciseness	The body is sectioned and mostly free of concept explanations Claude already knows, but generic filler like "Clarify goals, constraints, and required inputs" and "Apply relevant best practices and validate outcomes" could be tightened, matching the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	It offers only high-level hints and tool names ("Test with ExUnit", "Profile with :observer and :recon") with no executable Elixir code or concrete commands, fitting the minimal-concrete-guidance anchor rather than mostly-executable guidance.	2 / 5
Workflow Clarity	The numbered "Approach" list is a set of principles, not a sequenced workflow, and the "Instructions" bullets are vague with no validation checkpoints, matching the rough-sequence-with-gaps anchor.	2 / 5
Progressive Disclosure	Sections are clearly organized (Use when / Do not use / Focus Areas / Approach / Output), but the single external reference "resources/implementation-playbook.md" points to a file that does not exist in the bundle, leaving the reference broken rather than well-signaled.	3 / 5
	Total	10 / 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 uses natural Elixir trigger terms within a clear niche, but it omits any explicit "Use when..." guidance, which caps its completeness. Adding a concrete trigger clause would meaningfully raise the score.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing Elixir/OTP code, building Phoenix LiveView apps, or designing supervised concurrent systems."

Include common synonyms and file extensions users actually say, such as ".ex", ".exs", "mix", "BEAM", or "Ecto".

Tighten the broad closing sentence ("Masters concurrency, fault tolerance, and distributed systems") into specific actions to reduce overlap with generic concurrency skills.

Dimension	Reasoning	Score
Specificity	Names the Elixir domain plus several concrete capabilities ("OTP patterns, supervision trees, and Phoenix LiveView", "concurrency, fault tolerance, and distributed systems"), matching the anchor for several specific actions with minor gaps rather than a fully comprehensive action list.	4 / 5
Completeness	It clearly states what the skill does ("Write idiomatic Elixir code with OTP patterns...") but provides no "Use when..." trigger clause, so per the judging guidelines completeness is capped at 3 with the "when" missing.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ("Elixir", "OTP", "supervision trees", "Phoenix LiveView", "concurrency"), giving good keyword coverage, but omits common synonyms and file extensions like .ex/.exs.	4 / 5
Distinctiveness Conflict Risk	The Elixir/OTP/Phoenix LiveView niche is mostly distinct with minimal conflict risk, but the broad "Masters concurrency, fault tolerance, and distributed systems" phrasing leaves minor overlap with general Elixir or concurrency skills.	4 / 5
	Total	15 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/elixir-pro/SKILL.md
Commit: 57c135b

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