Skip to content
TrustedSkillsbeta
Back to all skills

Electron Release

Checked
laststance·vlatest·frontend·MIT

Automates controlled software deployments by precisely managing container image releases and rollback procedures.

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 laststance/skills --skill electron-release -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

laststance

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 laststance/skills at 66d87e7906.

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

Commit
66d87e7906
Manifest
skills/electron-release/SKILL.md
Scanned
1 file, 166 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 release process for Electron applications. It handles version bumping, asset management, code signing (if configured), and package creation for distribution across multiple platforms like Windows, macOS, and Linux. The resulting packages are ready for deployment to users or application stores.

When to use it

  • You're building a desktop application using the Electron framework.
  • You need to regularly release new versions of your application.
  • You want to streamline the process of creating installers for different operating systems.
  • You require code signing for distribution on platforms like macOS and Windows.

Key capabilities

  • Automated version bumping (e.g., semantic versioning)
  • Cross-platform package creation (Windows, macOS, Linux)
  • Code signing support
  • Asset management

Example prompts

  • "Release the current Electron application with version 1.2.3."
  • "Create a Windows installer for my Electron app."
  • "Prepare a release package including code signing for macOS."

Tips & gotchas

This skill requires an existing Electron project structure and potentially configuration for code signing certificates, which may need to be set up beforehand. Ensure your package.json is correctly formatted for optimal results.