elixir-pro

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

Quality

38%

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 ./skills/elixir-pro/SKILL.md

Quality

Content

25%Scale 1-5

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

This skill is essentially a high-level description of Elixir/OTP expertise areas rather than actionable guidance. It contains no code examples, no concrete commands, and no specific patterns that would help Claude perform better than it already would with its base knowledge. The content reads like a job description or capability summary rather than a teaching document.

Suggestions

Add concrete, executable code examples for key patterns (e.g., a GenServer template, a Supervisor child spec, a Phoenix LiveView skeleton) — these are the core value a skill should provide.

Replace vague instructions like 'Apply relevant best practices' with specific, actionable steps such as 'When creating a GenServer, always define handle_info for unexpected messages' with code.

Provide the referenced `resources/implementation-playbook.md` bundle file, or inline the most critical content if the file doesn't exist.

Add a concrete workflow with validation steps, e.g., 'mix compile --warnings-as-errors' after code changes, 'mix dialyzer' for type checking, 'mix test' for verification.

Dimension	Reasoning	Score
Conciseness	The skill contains some unnecessary padding (generic 'Use this skill when' / 'Do not use this skill when' sections that add no value, and vague instructions like 'Clarify goals, constraints, and required inputs'). The focus areas and approach sections are reasonably concise but read more like a general description of Elixir than actionable skill content Claude doesn't already know.	3 / 5
Actionability	The skill provides no concrete code examples, no executable commands, and no specific patterns. Everything is abstract guidance like 'Use pattern matching over conditional logic' and 'Embrace let it crash philosophy' — things Claude already knows and that provide no executable specificity.	1 / 5
Workflow Clarity	The 'Approach' section lists a rough sequence of principles rather than actionable workflow steps. There are no validation checkpoints, no feedback loops, and no clear process for how to actually build an OTP application or Phoenix project step by step.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` but no bundle files are provided, making this a dead reference. The content that is present is a flat list of bullet points with no meaningful structure or navigation to deeper materials. The reference to the playbook is buried in the instructions rather than clearly signaled.	2 / 5
	Total	8 / 20 Passed

Description

52%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 identifies the Elixir/OTP domain well with relevant technical terms that serve as good trigger keywords. However, it lacks a 'Use when...' clause entirely, and the phrase 'Masters concurrency' is a vague claim rather than a concrete capability description. Adding explicit trigger guidance and replacing buzzword claims with specific actions would significantly improve it.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about Elixir, OTP, GenServer, Phoenix LiveView, or BEAM-based applications'.

Replace the vague claim 'Masters concurrency, fault tolerance, and distributed systems' with concrete actions like 'Implements GenServers, builds supervision trees, configures distributed node clusters, and creates Phoenix LiveView interfaces'.

Include additional natural trigger terms users might say, such as 'GenServer', 'BEAM', 'mix', 'Ecto', '.ex files', or 'Phoenix channels'.

Dimension	Reasoning	Score
Specificity	Names the domain (Elixir) and mentions several concepts (OTP patterns, supervision trees, Phoenix LiveView, concurrency, fault tolerance, distributed systems), but these are more like topic areas than concrete actions. 'Write idiomatic Elixir code' is one concrete action, but 'Masters concurrency' is vague and uses a buzzword-like claim rather than describing specific capabilities.	3 / 5
Completeness	Has a reasonable 'what' (write Elixir code with OTP patterns, etc.) but completely lacks a 'when' clause. There is no 'Use when...' guidance or equivalent trigger phrasing, which per the rubric should cap completeness at 3, and the 'what' itself mixes concrete actions with vague claims like 'Masters concurrency', pushing it toward 2.	2 / 5
Trigger Term Quality	Includes strong natural keywords users would say: 'Elixir', 'OTP', 'supervision trees', 'Phoenix LiveView', 'concurrency', 'fault tolerance', 'distributed systems'. Missing some common variations like 'GenServer', 'BEAM', '.ex files', 'mix', 'Ecto', or 'channels' that users might naturally mention.	4 / 5
Distinctiveness Conflict Risk	Elixir is a specific enough language ecosystem that this skill is fairly distinct. The mention of OTP, supervision trees, and Phoenix LiveView further narrows the niche. Minor overlap risk with general 'write code' or 'web development' skills, but the Elixir-specific terminology makes it mostly distinguishable.	4 / 5
	Total	13 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: 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.