Skip to content
TrustedSkillsbeta
Back to all skills

Elixir Dependency Updater

Checked
tylercannon·vlatest·backend·MIT

Automatically updates your Elixir project’s dependencies to the latest versions, ensuring security and leveraging new features.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tylercannon/agent-skills --skill elixir-dependency-updater -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

tylercannon

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned tylercannon/agent-skills at 905b1ff57b.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
905b1ff57b
Manifest
skills/elixir-dependency-updater/SKILL.md
Scanned
1 file, 120 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The elixir-dependency-updater skill automates the process of updating Elixir project dependencies. It analyzes a project's mix.exs file, identifies outdated dependencies, and generates commands to update them safely. This ensures projects stay current with security patches and new features while minimizing potential breakage.

When to use it

  • Routine Maintenance: Regularly keep your Elixir projects up-to-date without manual effort.
  • Dependency Audits: Quickly identify which dependencies require updates during a security audit.
  • Automated Build Pipelines: Integrate dependency updates into CI/CD pipelines for consistent and reliable releases.
  • Large Projects: Streamline the update process for projects with numerous dependencies, reducing tedious manual work.

Key capabilities

  • Analyzes mix.exs files to identify outdated dependencies.
  • Generates commands for updating dependencies.
  • Supports safe dependency updates.

Example prompts

  • "Update all Elixir dependencies in my project."
  • "Show me the outdated dependencies in my current Elixir project."
  • “Generate a list of commands to update the phoenix dependency.”

Tips & gotchas

  • Requires access to an Elixir project's codebase.
  • Always review generated commands before execution, especially in production environments.