Skip to content
TrustedSkillsbeta
Back to all skills

Evm Deployment

Checked
sablier-labs·vlatest·devops·MIT

Automates Ethereum Virtual Machine (EVM) smart contract deployments to testnets and mainnet using Sablier Labs' infrastructure.

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 sablier-labs/agent-skills --skill evm-deployment -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

sablier-labs

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 sablier-labs/agent-skills at 41e29982b5.

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

Commit
41e29982b5
Manifest
skills/evm-deployment/SKILL.md
Scanned
5 files, 928 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

This skill automates the deployment of Ethereum Virtual Machine (EVM) smart contracts. It handles tasks such as compiling Solidity code, interacting with blockchain networks, and verifying contract deployments. The skill streamlines the process of deploying decentralized applications (dApps) and other EVM-based projects.

When to use it

  • Deploying a new smart contract to a testnet like Goerli or Sepolia.
  • Automating the deployment process as part of a CI/CD pipeline.
  • Verifying that a deployed contract matches its source code on a blockchain explorer.
  • Updating an existing smart contract with a new version.

Key capabilities

  • Solidity compilation
  • Blockchain interaction (likely via RPC calls)
  • Contract verification
  • Automated deployment workflows

Example prompts

  • "Deploy the 'MyToken' contract to Goerli."
  • "Verify the deployed contract at address 0x123..."
  • “Run the deployment script for my dApp.”

Tips & gotchas

The skill requires access to a blockchain network (e.g., via API keys or RPC endpoints). Ensure you have configured these credentials correctly before attempting deployments.