elixir-otp
OTP design patterns, supervision trees, and process management with KISS principle emphasis
55
58%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skill/elixir-otp/SKILL.mdQuality
Discovery
32%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 a specific technical domain (OTP/Erlang/Elixir) but lacks concrete actions and completely omits trigger guidance for when Claude should use this skill. The KISS principle mention adds little value for skill selection. It needs explicit 'Use when...' triggers and more specific capability descriptions.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Elixir', 'Erlang', 'GenServer', 'supervisor', 'fault-tolerant', 'actor model', or 'BEAM'.
Replace vague 'design patterns' with specific actions like 'implement GenServers, design supervisor hierarchies, structure OTP applications'.
Include common file extensions or project indicators like '.ex', 'mix.exs', or 'umbrella projects' to improve trigger matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (OTP, Erlang/Elixir) and mentions some concepts (design patterns, supervision trees, process management), but doesn't list concrete actions like 'create GenServers', 'design fault-tolerant systems', or 'implement supervisors'. | 2 / 3 |
Completeness | Only addresses 'what' at a high level with no 'Use when...' clause or explicit trigger guidance. Missing any indication of when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'OTP', 'supervision trees', and 'process management' that users familiar with Erlang/Elixir would use, but misses common variations like 'GenServer', 'Elixir', 'Erlang', 'fault tolerance', or 'actor model'. | 2 / 3 |
Distinctiveness Conflict Risk | 'OTP' and 'supervision trees' are fairly specific to Erlang/Elixir ecosystem, reducing conflict risk, but 'design patterns' and 'process management' are generic terms that could overlap with other programming skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong OTP skill with excellent actionable code examples and clear workflow guidance following the KISS principle. The decision framework for when to use each pattern is particularly valuable. The main weakness is verbosity - explanatory prose like 'When to use' sections and pattern descriptions could be trimmed since Claude understands these concepts.
Suggestions
Remove or significantly condense 'When to use X' sections - Claude understands when GenServers, Supervisors, and Tasks are appropriate
Trim explanatory prose around code examples (e.g., 'Basic GenServer Pattern:' followed by 'When to use GenServer:' is redundant)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations like 'When to use GenServer' lists that Claude already understands. The code examples are valuable but the surrounding prose could be tightened significantly. | 2 / 3 |
Actionability | Excellent executable code examples throughout - GenServer patterns, Supervisor configurations, Task usage, and testing patterns are all copy-paste ready with complete implementations including callbacks and client APIs. | 3 / 3 |
Workflow Clarity | Clear decision framework with explicit progression: 'Start Simple (80% of cases)' → 'Advance When Needed' → 'Profile to find actual bottlenecks' → 'Measure improvement, iterate'. The KISS emphasis provides clear guidance on when to use each pattern. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from essential patterns to advanced patterns. Cross-references to related skills (elixir-architecture, elixir-phoenix-framework, elixir-review) are clearly signaled at the end. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (655 lines); consider splitting into references/ and linking | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 13 / 16 Passed | |
- Repository
- vircung/opencode-config
- Commit
e2b74bf
- 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.