elixir-pro
Build Reliable Elixir and Phoenix Systems
Elixir projects require careful decisions about concurrency, supervision, data boundaries, testing, and performance. This skill provides focused guidance for idiomatic, fault-tolerant implementations.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "elixir-pro" from https://skillstore.io/skills/sickn33-elixir-pro.md and its manifest at https://skillstore.io/api/skills/sickn33-elixir-pro/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "elixir-pro". Design supervision for a queue consumer, connection pool, and metrics reporter.
Expected outcome:
Recommended design: isolate the connection pool, supervise queue consumers dynamically, and keep metrics reporting independent. Test restart behavior and dependency loss.
Using "elixir-pro". Review a LiveView that performs validation and database writes inside event handlers.
Expected outcome:
Move business operations into a context, retain presentation state in LiveView, validate through changesets, enforce authorization, and test both context and interface behavior.
Using "elixir-pro". Investigate rising scheduler utilization after traffic doubles.
Expected outcome:
First correlate scheduler, mailbox, garbage collection, and latency metrics. Reproduce the workload, profile measured hotspots, benchmark isolated changes, and compare results.
Security Audit
SafeThe sole static finding is a false positive caused by Markdown backticks around a referenced file path. No command execution or malicious intent appears in SKILL.md.
Risk Factors
⚙️ External commands (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-elixir-pro/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-elixir-pro?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-elixir-pro?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-elixir-pro/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-elixir-pro.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). elixir-pro security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-elixir-pro/audits/5BibTeX citation
@techreport{sickn33-sickn33-elixir-pro-2026,
author = {sickn33},
title = {elixir-pro security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-elixir-pro/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "elixir-pro security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-elixir-pro/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-elixir-pro:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Structure a New OTP Service
Plan process ownership, supervision boundaries, restart behavior, and test coverage for a new service.
Improve a Phoenix Application
Review contexts, LiveView state, Ecto changesets, and application boundaries for maintainability.
Diagnose BEAM Performance
Develop a measurement plan using Telemetry, Benchee, Observer, and Recon before changing system behavior.
Try These Prompts
Review this Elixir module for idiomatic pattern matching, guard clauses, clear errors, and testability. Explain each recommendation and propose focused tests.
Design an OTP supervision tree for these workers and dependencies: [details]. Define ownership, restart strategies, failure boundaries, startup order, and ExUnit tests.
Plan this Phoenix LiveView feature: [requirements]. Separate context logic, Ecto validation, LiveView state, events, authorization checks, telemetry, and integration tests.
Analyze these symptoms and measurements from a clustered Elixir system: [evidence]. Form hypotheses, rank risks, and design Observer, Recon, Telemetry, and Benchee experiments.
Best Practices
- Provide Elixir, Erlang, Phoenix, Ecto, and dependency versions with each request.
- Describe process ownership, expected failures, workload, and recovery requirements before selecting OTP patterns.
- Validate recommendations with ExUnit, Dialyzer, benchmarks, telemetry, and representative production conditions.
Avoid
- Do not add processes when a pure function or existing process already provides clear ownership.
- Do not choose supervision strategies without defining expected failures and restart dependencies.
- Do not optimize BEAM behavior before collecting representative measurements.