elixir-pro

Write idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView. Masters concurrency, fault tolerance, and distributed systems. Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM optimizations.

Quality

65%

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

40%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 and concise but largely generic: it describes Elixir expertise in the abstract without executable code, concrete workflows, or validation steps. It reads more like a topic outline than an actionable skill.

Suggestions

Replace the generic Instructions and 'Use this skill when' boilerplate with Elixir-specific triggers and a concrete worked example (e.g., a supervised GenServer with a child_spec).

Add at least one executable code snippet or command per focus area (e.g., `mix new --sup`, an ExUnit async test, a Benchee benchmark skeleton) to lift actionability.

Turn the Approach principles into a sequenced workflow with explicit validation checkpoints (e.g., 'run `mix test --cover`', 'run `mix credo`', 'run `dialyzer`') so steps are verifiable rather than abstract.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not over-explain concepts Claude already knows, but it includes generic templated filler ('Working on elixir pro tasks or workflows', 'Apply relevant best practices and validate outcomes') that adds little Elixir-specific value.	3 / 5
Actionability	Guidance is high-level and descriptive ('Embrace let it crash philosophy', 'Use pattern matching over conditional logic') with no executable code or commands; it names some tools (ExUnit, :observer, Benchee, Dialyzer) but never shows how to use them.	2 / 5
Workflow Clarity	The numbered Approach list is a set of design principles rather than a sequenced workflow, and there are no validation checkpoints or error-recovery feedback loops for the destructive/optimization operations the skill covers.	2 / 5
Progressive Disclosure	The single-file body is well organized into clearly labeled sections (Focus Areas, Approach, Output) and needs no external references at this length, though the generic 'Use this skill when' boilerplate slightly dilutes navigation value.	4 / 5
	Total	11 / 20 Passed

Description

91%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 strong: it names concrete capabilities, gives explicit trigger guidance, and occupies a distinct niche. The only weakness is mild over-claiming ('Masters') and a few missing natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists several specific concrete actions and domains ('Write idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView', 'Elixir refactoring, OTP design, or complex BEAM optimizations'), but 'Masters concurrency, fault tolerance, and distributed systems' is a capability claim rather than an action, leaving minor gaps.	4 / 5
Completeness	Explicitly answers both what ('Write idiomatic Elixir code with OTP patterns... Masters concurrency, fault tolerance, and distributed systems') and when ('Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM optimizations') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural terms users would say ('Elixir refactoring', 'OTP design', 'BEAM optimizations', 'Phoenix LiveView'), but missing common synonyms/extensions such as Erlang, Mix, or Ecto.	4 / 5
Distinctiveness Conflict Risk	Clear niche around Elixir/BEAM/OTP with distinct triggers ('Elixir refactoring', 'OTP design', 'BEAM optimizations'); minimal overlap risk with other skills.	5 / 5
	Total	18 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/elixir-pro/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.