CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

elixir-development

Modern Elixir idioms, functional patterns, testing strategies, and implementation best practices

Quality

62%

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 ./skill/elixir-development/SKILL.md
SKILL.md
Quality
Evals
Security

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 a well-organized, code-rich Elixir reference with strong actionability, though it is longer than necessary and inlines content that could live in separate reference files. It re-teaches some basic concepts Claude already knows and lacks any bundle-based progressive disclosure.

Suggestions

Trim or remove sections that re-teach basics Claude already knows (basic pattern matching, list comprehensions, simple recursion/TCO) to recover token budget.

Move large reference blocks (e.g., the full testing-strategies and version-features material) into files under references/ and point to them from SKILL.md to improve progressive disclosure.

Make at least one representative example per topic fully self-contained and runnable (with defined helpers or ExUnit doctests) so examples are copy-paste ready rather than illustrative templates.

DimensionReasoningScore

Conciseness

The body is mostly concrete code examples that assume competence, but sections on basic pattern matching, list comprehensions, and recursion/tail-call optimization re-teach concepts Claude already knows, and the ~660-line volume could be tightened, fitting 'Mostly efficient but includes some unnecessary explanation.'

3 / 5

Actionability

Abundant syntactically-valid Elixir code covers common cases (pipes, with, comprehensions, protocols, ExUnit/Mox), but many examples call undefined helpers like create_user, validate_order, and insert(:user), making them illustrative templates rather than standalone copy-paste, matching 'Mostly executable guidance... with minor gaps.'

4 / 5

Workflow Clarity

This is a reference/idiom skill with no destructive or batch operations requiring validation, and the content is clearly organized into well-sequenced topical sections plus a Best Practices summary, giving clear organization with only minor gaps.

4 / 5

Progressive Disclosure

Header structure is good and the Cross-References section clearly signals sibling skills, but no bundle files exist and all content (idioms, testing, version features) is inlined in one ~660-line file rather than split into reference files, fitting 'Some structure... content that should be separate is inline.'

3 / 5

Total

14

/

20

Passed

Description

45%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 identifies the Elixir domain and several relevant topic areas, but it lacks concrete actions and any explicit 'when to use' trigger guidance, capping completeness at 3. Trigger terms are relevant but miss common variations and synonyms.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when writing or refactoring Elixir code, adding ExUnit tests, or applying functional patterns').

Replace abstract noun-categories with concrete verbs (e.g., 'Write idiomatic Elixir, structure error handling with `with`, and build ExUnit test suites') to lift specificity.

Include natural variations users actually say (ExUnit, mix, .ex files) to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

Names the Elixir domain plus four topic areas ('idioms, functional patterns, testing strategies, and implementation best practices'), but these are abstract noun-categories with no concrete verbs or actions, matching 'Names the domain but actions are minimal or generic.'

2 / 5

Completeness

A clear 'what' is present (the covered topic areas), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the missing-trigger rule completeness is capped at 3.

3 / 5

Trigger Term Quality

'Elixir', 'idioms', 'functional patterns', and 'testing' are relevant natural keywords, but common variations and synonyms like '.ex', 'ExUnit', 'mix', or 'Elixir code' are missing, fitting 'Some relevant keywords but missing common variations or synonyms.'

3 / 5

Distinctiveness Conflict Risk

'Elixir' is a genuine niche, but the broad scope ('testing strategies', 'implementation best practices') overlaps with the sibling elixir-ecto/otp/phoenix skills, matching 'Somewhat specific but could still overlap with similar skills.'

3 / 5

Total

11

/

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

skill_md_line_count

SKILL.md is long (671 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

vircung/opencode-config

Path

skill/elixir-development/SKILL.md

Revision

e2b74bf

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill