BF erlang-distribution
Use when erlang distributed systems including node connectivity, distributed processes, global name registration, distributed supervision, network partitions, and building fault-tolerant multi-node applications on the BEAM VM.
As a process F 28/100 · Will not run — References files that are not bundled: <https://www.erlang.org/doc/apps/erts/erl_dist_protocol.html>, <https://www.erlang.org/doc/reference_manual/distributed.html>, <https://learnyousomeerlang.com/distributed-otp-applications>
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: <https://www.erlang.org/doc/apps/erts/erl_dist_protocol.html> - warning
missing-refreference to a missing file: <https://www.erlang.org/doc/reference_manual/distributed.html> - warning
missing-refreference to a missing file: <https://learnyousomeerlang.com/distributed-otp-applications> - warning
missing-refreference to a missing file: <https://www.oreilly.com/library/view/designing-distributed-systems/9781491983638/> - warning
missing-refreference to a missing file: <https://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed/>
Process rating: all ten parameters 28/100
- 0Tools and files. 5 referenced file(s) missing: <https://www.erlang.org/doc/apps/erts/erl_dist_protocol.html>, <https://www.erlang.org/doc/reference_manual/distributed.html>, <https://learnyousomeerlang.com/distributed-otp-applications>
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (erlang-distribution) differs from the folder (fix-erlang-ssh-cve-erlang-distribution)
- 100Steps. 25 steps
- 100Execution cost. Instruction body is 3257 tokens
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 226: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.