Elixir Dev
v1.0.0Elixir/Phoenix development companion. Run and interpret mix test, mix credo, mix dialyzer, mix format. Generate modules following OTP conventions: contexts, schemas, GenServers, supervisors, tasks. Debug compilation errors and warnings. Help with Ecto migrations, queries, changesets, and associations. Use for any Elixir or Phoenix development task including writing modules, fixing tests, refactoring code, or understanding OTP patterns.
⭐ 1· 1.9k·2 current·2 all-time
by@gchapim
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the provided instructions and reference docs: mix commands, credo/dialyzer/format, OTP templates, Ecto patterns. There are no unexpected environment variables, binaries, or installs required.
Instruction Scope
The SKILL.md contains explicit runtime commands (mix test, mix ecto.migrate/rollback/drop, mix phx.server, etc.) and many code templates. This is appropriate for a dev companion, but some commands are destructive (e.g., mix ecto.drop, mix ecto.reset) or start servers; the agent may suggest running them — review and run in a safe environment (MIX_ENV=test or a container) before executing.
Install Mechanism
No install spec and no code files to write to disk; instruction-only skills are lowest-risk for installation. The regex scanner had no code to analyze.
Credentials
The skill declares no required environment variables or credentials. The docs include examples referencing common env vars (MIX_ENV, DATABASE_URL) which are normal examples for Elixir projects but are not requested by the skill itself.
Persistence & Privilege
always:false and no special privileges requested. The skill does not modify other skills or system-wide configs and does not request permanent presence.
Assessment
This skill appears coherent and is just documentation and command suggestions for Elixir/Phoenix development. Before using it: (1) review any recommended commands the agent wants to run — some are destructive (mix ecto.drop, mix ecto.reset) or start services; never run them on production data; (2) run commands in a safe environment (MIX_ENV=test, isolated container, or a backup copy of the DB); (3) confirm your project’s DATABASE_URL and credentials are correct and that you intend the side effects (migrations, drops, server start); and (4) note the skill source/homepage is unknown — if you need stronger assurance, prefer skills with a known repository or run the agent in a sandbox before granting it the ability to execute commands.Like a lobster shell, security has layers — review code before you run it.
latestvk97axg67jbtmvq38q3fwa3fspn80f8yv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.