ericrisco/rsc-harness / skills/elixir
elixir
VerifiedUse when writing or refactoring Elixir/OTP on the BEAM — GenServers, supervision trees and restart strategies, pattern matching, mix projects and releases — or when processes misbehave (restart loops, mailbox growth, call timeouts). NOT a Phoenix web app, LiveView, Ecto or channels (that is `phoenix`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.5 KB |
| evals/README.md | markdown | 860 B |
| evals/cases.yaml | config | 2.6 KB |
| references/mix-and-releases.md | markdown | 3.1 KB |
| references/otp-patterns.md | markdown | 4.1 KB |
| scripts/verify.shexecutable | script | 2.6 KB |
evals/README.md
View on GitHub# Evals: elixir
These cases are illustrative, not an automated grader. To run them by hand, read each `should_trigger` prompt and confirm the skill would fire (especially the non-obvious mailbox-growth and blocking-init cases and the Catalan/Spanish phrasings); then read each `should_not_trigger` prompt and confirm you would instead route to the named sibling (`phoenix` for web/LiveView/Ecto, `go` for goroutines, `postgresdb` for DB tuning) rather than answering as Elixir. For the `capability` case, give the scenario to the agent and check the produced code against the `must_include` rubric line by line — every item should be present and idiomatic (client/server split, DynamicSupervisor + Registry, child_spec, `@spec`, no blanket `try/rescue`, tagged tuples, a real mix layout). Score it as pass only if nothing in the rubric is missing or faked.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |