New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Prepare Release

by neetly in neetly/figma-agent-linux

Prepare a new figma-agent-linux release by updating the package version, changelog, and release links, then validating the changes.

MITAuto-check passedDevelopment

Install Prepare Release

skills CLI
$ npx skills add neetly/figma-agent-linux --skill prepare-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install neetly/figma-agent-linux prepare-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/neetly/figma-agent-linux.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prepare-release .claude/skills/prepare-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prepare-release
GitHub stars
394
Token cost
~833 tokens
SKILL.md length
430 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Prepare a new figma-agent-linux release by updating the package version, changelog, and release links, then validating the changes.

  • Release preparation
  • SKILL.md covers Version and baseline, Changelog and release notes and Validation and handoff
  • Calls cargo and git
  • A release version bump in this repository

What it does

Prepare Release is an agent skill from neetly/figma-agent-linux. Prepare a new figma-agent-linux release by updating the package version, changelog, and release links, then validating the changes. Use for release preparation or a release version bump in this repository.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. It works with Figma, Linux and GitHub. The repository describes itself as: Use locally installed fonts in Figma’s web app on Linux. (a.k.a. font helper). The licence is MIT.

When your agent uses it

  • Release preparation
  • A release version bump in this repository

Example prompts

  • “/prepare-release”

What it can do on your machine

Read from SKILL.md and the folder at commit 6f58726. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prepare Release loads about 833 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 430 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~833

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from neetly/figma-agent-linux at commit 6f58726, republished under its MIT licence (© neetly). 430 words, ~833 tokens.

Download SKILL.mdSave it as .claude/skills/prepare-release/SKILL.md (or your agent's skills folder).
name
prepare-release
description
Prepare a new figma-agent-linux release by updating the package version, changelog, and release links, then validating the changes. Use for release preparation or a release version bump in this repository.

Prepare a release

Read the repository's AGENTS.md, README.md, and CONTRIBUTING.md and inspect the working tree before editing. Preserve unrelated changes.

Version and baseline

  • Inspect Cargo.toml, release tags, and .github/workflows/release.yml to establish the current version and preceding release. Release tags use the bare package version, such as 0.4.5. Do not assume the manifest version has already been released or add compatibility for older tag formats.
  • Use the version requested by the user. Otherwise choose a patch bump for fixes and maintenance, or a minor bump for new features, and explain the choice. Ask if the intended version or release baseline cannot be established.
  • Update the package version in Cargo.toml and the figma-agent entry in Cargo.lock, without updating dependency versions or unrelated lock entries.

Changelog and release notes

  • Review commits and relevant diffs from the preceding release to the intended release commit, including pending changes that will ship. Summarize actual user-visible fixes and changes; group routine dependency maintenance.
  • Add an explicit anchor such as <a name="0.4.5"></a> followed by the version heading ## 0.4.5 at the top of CHANGELOG.md, below its introduction. Keep existing entries. The changelog begins at 0.4.4; do not backfill earlier releases.
  • Include a full comparison link using the actual preceding and planned tags. Do not invent a release date before one has been chosen.
  • Keep the GitHub release body linked to CHANGELOG.md at the release tag, with the bare tag as the anchor. Use github.repository and github.ref_name directly in the workflow URL and fragment. Explicit anchors preserve dots; GitHub-generated heading anchors remove them. Keep tags, headings, and explicit anchors consistent.
  • The tag-push workflow builds x86_64 and aarch64 Linux binaries and publishes the GitHub release. Preserve its artifact names because the installer uses them. No separate release branch is required by the current workflow.
Show full SKILL.md (137 more words)Show less

Validation and handoff

  • Run git diff --check and review the full release diff, including new files. Check version consistency, changelog scope, comparison tags, and workflow link/anchor expansion. Links to the new tag become available after publication.
  • For package version changes or Rust edits, use rust-toolchain.toml and run cargo +nightly fmt --check, cargo clippy -- --deny warnings, and cargo test. Report checks that failed or could not run. Documentation-only edits do not require Rust checks.
  • Report the chosen version, changelog coverage, validations actually run, and remaining limitations. Leave a reviewable diff when asked to prepare a release.
  • Commit, tag, push, or publish only when the user requests those actions. Before an authorized tag push, ensure the tagged commit contains the version bump and changelog and required checks have passed. Every AI-assisted commit needs the Co-authored-by: trailer required by CONTRIBUTING.md.

© neetly, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/prepare-release of neetly/figma-agent-linux.

Open the folder on GitHubat commit 6f58726

Compare with similar skills

Prepare Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prepare Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prepare Release this skillneetly/figma-agent-linux394—~833Automated safety check: PassMIT
Cut Releasejfernandez/bpftop2.7k—~2kAutomated safety check: PassApache-2.0
Release NotesMikalaiBarysevich/CleverSwitch115—~975Automated safety check: PassGPL-3.0
Releasemqtt-viewer/mqtt-viewer133—~1.8kAutomated safety check: PassGPL-3.0
Kernel Watch Triageantoinecellerier/speaker-tuning-to-easyeffects142—~2.6kAutomated safety check: PassMIT
Releasing MarchatCod-e-Codes/marchat137—~801Automated safety check: PassMIT

Similar skills

  • Cut Release

    jfernandez/bpftop

    Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.

    2.7k GitHub stars~2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Release Notes

    MikalaiBarysevich/CleverSwitch

    Generate GitHub release notes for unreleased CleverSwitch tags in the established repo format.

    115 GitHub stars~975 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Release

    mqtt-viewer/mqtt-viewer

    Publish a MQTT Viewer release end to end. An agent skill from mqtt-viewer/mqtt-viewer.

    133 GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Kernel Watch Triage

    antoinecellerier/speaker-tuning-to-easyeffects

    Guides triaging a kernel-sound-watch hit comment on the "Kernel sound-tree watch" issue (40) — the weekly workflow's per-tag report of .github/kernel-watchlist.txt grep hits against a new…

    142 GitHub stars~2.6k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Releasing Marchat

    Cod-e-Codes/marchat

    Prepares marchat releases: version bumps, CHANGELOG, packaging checksums, GitHub Actions release workflow, and Docker tags.

    137 GitHub stars~801 tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed

  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed

Works with

Categories

Questions about Prepare Release

What does Prepare Release do?

Prepare a new figma-agent-linux release by updating the package version, changelog, and release links, then validating the changes. Prepare Release is an agent skill from neetly/figma-agent-linux. Prepare a new figma-agent-linux release by updating the package version, changelog, and release links, then validating the changes.

When should I use Prepare Release?

Prepare Release fits situations like: release preparation; A release version bump in this repository.

How do I install Prepare Release in Claude Code?

Run `npx skills add neetly/figma-agent-linux --skill prepare-release -a claude-code`. Or copy the skill folder (.agents/skills/prepare-release in neetly/figma-agent-linux) into .claude/skills/prepare-release in your project. Claude Code loads it when a task matches its description.

How do I install Prepare Release in Codex?

Run `npx skills add neetly/figma-agent-linux --skill prepare-release -a codex`. Or copy the skill folder (.agents/skills/prepare-release in neetly/figma-agent-linux) into .agents/skills/prepare-release in your project. Codex loads it when a task matches its description.

Can I use Prepare Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add neetly/figma-agent-linux --skill prepare-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prepare-release, .gemini/skills/prepare-release, .github/skills/prepare-release and .opencode/skills/prepare-release in your project.

What does Prepare Release need to run?

Going by SKILL.md and its folder, Prepare Release needs the command-line tools its instructions call (cargo and git).

Does Prepare Release access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Prepare Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prepare Release use?

Prepare Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prepare Release use?

About 833 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prepare Release?

Skills that share tags, products or a category with Prepare Release: Cut Release (jfernandez/bpftop, 2.7k stars), Release Notes (MikalaiBarysevich/CleverSwitch, 115 stars), Release (mqtt-viewer/mqtt-viewer, 133 stars) and Kernel Watch Triage (antoinecellerier/speaker-tuning-to-easyeffects, 142 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prepare Release?

neetly (a GitHub organization) maintains it in neetly/figma-agent-linux, which has 394 GitHub stars. The repository was last updated on October 4, 2026.

Source: neetly/figma-agent-linux on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.