CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

elixir-pro

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/elixir-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

43%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-organized and token-lean in its lists, but it operates entirely at the topic-name level: no executable code, commands, or worked examples, and its 'workflow' is a list of principles rather than a sequenced process with validation. Roughly a third of the content is generic boilerplate unrelated to Elixir.

Suggestions

Replace the generic 'Use this skill when / Do not use this skill when / Instructions' boilerplate with Elixir-specific triggers (e.g., 'when editing .ex/.exs files, designing GenServers or supervision trees, or building Phoenix LiveViews') and a concrete first step.

Add executable examples for the lowest-effort wins: a minimal GenServer + Supervisor child spec snippet, a property-based ExUnit test with StreamData, and the actual mix/dialyzer/benchee commands to run.

Restructure 'Approach' into a sequenced workflow with validation checkpoints, e.g.: write/change code → run `mix test` and `mix dialyzer` → if dialyzer or tests fail, fix and re-run → only then profile with :observer/:recon and benchmark with Benchee.

DimensionReasoningScore

Conciseness

The Focus Areas / Approach / Output lists are lean, but roughly a third of the body is generic template filler that adds nothing Claude doesn't know: "Working on elixir pro tasks or workflows", "Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes." That is more than the 'minor instances' of anchor 4, fitting anchor 3 ('mostly efficient but includes some unnecessary explanation').

3 / 5

Actionability

There is no code, command, or example anywhere — only high-level hints and tool name-drops like "Profile with :observer and :recon for bottlenecks" and "Performance benchmarks with Benchee". This matches anchor 2 ('minimal concrete guidance; high-level hints but missing the specific steps to execute'); it does not reach anchor 3 because even incomplete concrete guidance (pseudocode or partial steps) is absent.

2 / 5

Workflow Clarity

The numbered "Approach" list ("1. Embrace 'let it crash' philosophy... 2. Use pattern matching over conditional logic...") is a set of parallel design principles, not a sequenced process, and validation appears only as boilerplate ("Apply relevant best practices and validate outcomes") with no actual checkpoints — matching anchor 2 ('rough sequence present but many gaps; steps poorly defined; validation absent').

2 / 5

Progressive Disclosure

The body is under 50 lines with no bundle files and no content that warrants external references, and it is organized into clear sections (Use when / Do not use / Instructions / Focus Areas / Approach / Output). Per the rubric's simple-skill guideline, this earns anchor 5 ('well-organized sections' with no need for external references).

5 / 5

Total

12

/

20

Passed

Description

78%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.

A strong description: it names the domain with multiple specific capabilities and includes an explicit 'Use for...' trigger clause with concrete terms. Weaknesses are the buzzword-y "Masters concurrency, fault tolerance, and distributed systems" sentence and a when-clause that misses natural Phoenix/Ecto trigger phrasing.

DimensionReasoningScore

Specificity

Quotes several concrete capabilities — "Write idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView", "Use for Elixir refactoring, OTP design, or complex BEAM optimizations" — but the middle sentence "Masters concurrency, fault tolerance, and distributed systems" is a fluffy claim rather than a concrete action, leaving minor coverage gaps versus the comprehensive anchor 5.

4 / 5

Completeness

Both parts are present: a clear "what" ("Write idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView") and an explicit "when" ("Use for Elixir refactoring, OTP design, or complex BEAM optimizations"). The when-clause is concrete but task-type framed rather than user-utterance framed and omits Phoenix/Ecto triggers, matching anchor 4 ('when' could be more explicit or specific) rather than anchor 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "Elixir", "OTP", "supervision trees", "Phoenix LiveView", "BEAM", "refactoring" are terms users would actually say. A few common variations are missing (e.g., Ecto, GenServer, mix, .ex/.exs file extensions), so it falls just short of the comprehensive synonym/extension coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Quotes "OTP patterns, supervision trees, and Phoenix LiveView" and "complex BEAM optimizations" — a clear, well-defined niche with distinct trigger terms that would rarely fire for unrelated skills, matching anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/elixir-pro/SKILL.md

Reviewed

Table of Contents

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.