New: 98,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

Phoenix Release Please

by Arize-ai in Arize-ai/phoenix

Bump the next release-please version for a Phoenix Python package (arize-phoenix, arize-phoenix-client, arize-phoenix-evals, arize-phoenix-otel) by opening a PR with a Release-As commit footer.

Apache-2.0Auto-check passedAI & LLM Engineering

Install Phoenix Release Please

skills CLI
$ npx skills add Arize-ai/phoenix --skill phoenix-release-please -a claude-code

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

GitHub CLI
$ gh skill install Arize-ai/phoenix phoenix-release-please --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/Arize-ai/phoenix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/phoenix-release-please .claude/skills/phoenix-release-please && 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
phoenix-release-please
GitHub stars
12k
Token cost
~708 tokens
SKILL.md length
236 words
Files
1
Skills in repo
39
Repo updated
First seen
Licence
Apache-2.0

At a glance

Bump the next release-please version for a Phoenix Python package (arize-phoenix, arize-phoenix-client, arize-phoenix-evals, arize-phoenix-otel) by opening a PR with a Release-As commit footer.

  • Works in 5 steps: Verify the bump. jq .… → Branch off main. → Make a small real edit inside the… → …
  • The user asks to set the release-please version
  • SKILL.md covers Packages, Procedure, Squash-merge gotcha and Bumping arize-phoenix (root)
  • Calls git, jq and gh

What it does

Phoenix Release Please is an agent skill from Arize-ai/phoenix. Bump the next release-please version for a Phoenix Python package (arize-phoenix, arize-phoenix-client, arize-phoenix-evals, arize-phoenix-otel) by opening a PR with a Release-As commit footer. Use this skill when the user asks to "set the release-please version", "force a 2.0.0 release", "release X as Y", "skip a version", or otherwise wants release-please to propose a specific version on its next run instead of the version it would pick from conventional commits.

Its SKILL.md is about 710 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 AI & LLM Engineering, covering LLM observability, LLM evaluation and Commit messages. It works with Arize Phoenix, OpenTelemetry and Python. The repository describes itself as: AI Observability & Evaluation. The licence is Apache-2.0.

When your agent uses it

  • The user asks to set the release-please version
  • Force a 2.0.0 release
  • Otherwise wants release-please to propose a specific version on its next run instead of the version it would pick from conventional commits

Example prompts

  • “set the release-please version”
  • “force a 2.0.0 release”
  • “release X as Y”
  • “/phoenix-release-please”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Verify the bump. jq . .release-please-manifest.json — target must be strictly greater
  2. Branch off main.
  3. Make a small real edit inside the package path (typo fix, comment cleanup). Without a
  4. Commit with the trailer in the body
  5. Open the PR with chore: title and the trailer also at the end of the PR body

What it can do on your machine

Read from SKILL.md and the folder at commit 856100b. 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:

    • git
    • jq
    • gh

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

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    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

Phoenix Release Please loads about 708 tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 236 words of instructions outside code blocks.

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

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 Arize-ai/phoenix at commit 856100b, republished under its Apache-2.0 licence (© Arize-ai). 236 words, ~708 tokens.

Download SKILL.mdSave it as .claude/skills/phoenix-release-please/SKILL.md (or your agent's skills folder).
name
phoenix-release-please
description
Bump the next release-please version for a Phoenix Python package (arize-phoenix, arize-phoenix-client, arize-phoenix-evals, arize-phoenix-otel) by opening a PR with a Release-As commit footer. Use this skill when the user asks to "set the release-please version", "force a 2.0.0 release", "release X as Y", "skip a version", or otherwise wants release-please to propose a specific version on its next run instead of the version it would pick from conventional commits.
license
Apache-2.0
metadata.author
oss@arize.com
metadata.version
1.0.0
metadata.internal
true

Phoenix release-please version bump

Force release-please to propose a specific next version for a managed package by landing a commit with a Release-As trailer.

Packages

Declared in release-please-config.json; current versions in .release-please-manifest.json.

PathPackage
.arize-phoenix (root has exclude-paths; touch a file outside them, e.g. src/phoenix/)
packages/phoenix-clientarize-phoenix-client
packages/phoenix-evalsarize-phoenix-evals
packages/phoenix-otelarize-phoenix-otel

Procedure

  1. Verify the bump. jq . .release-please-manifest.json — target must be strictly greater than the current entry.

  2. Branch off main.

  3. Make a small real edit inside the package path (typo fix, comment cleanup). Without a file change in that path, release-please ignores the commit. Don't edit pyproject.toml's version or .release-please-manifest.json — release-please owns those.

  4. Commit with the trailer in the body:

    bash
    git commit -m "$(cat <<'EOF'
chore: release <package> <version>

<one-line rationale>

Release-As: <version>
EOF
)"

  5. Open the PR with chore: title and the trailer also at the end of the PR body (defensive, in case squash settings change).

Squash-merge gotcha

Repo settings (verify with gh api repos/Arize-ai/phoenix --jq '{squash_merge_commit_title, squash_merge_commit_message}'): COMMIT_OR_PR_TITLE + COMMIT_MESSAGES. The squash body comes from commit messages, not the PR description — so Release-As must live in a real commit's body. A trailer that exists only in the PR description is dropped on squash and release-please never sees it.

Bumping arize-phoenix (root)

The root package's entry in release-please-config.json lists many exclude-paths (.github, docs, js, packages, tests, tutorials, …). A change inside any of those paths is not counted as a server change. Pick a file under src/phoenix/ (or another non-excluded path) for the path-touching edit.

© Arize-ai, Apache-2.0. 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/phoenix-release-please of Arize-ai/phoenix.

Open the folder on GitHubat commit 856100b

Compare with similar skills

Phoenix Release Please 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.

Phoenix Release Please compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Phoenix Release Please this skillArize-ai/phoenix12k—~708Automated safety check: PassApache-2.0
Phoenix LLM ObservabilityOrchestra-Research/AI-Research-SKILLs13k2 repos~2.9kAutomated safety check: PassMIT
Failproof AI SDK IntegrationFailproofAI/failproofai5.3k—~6kAutomated safety check: PassCustom licence
Logfire Evalspydantic/skills140—~3.6kAutomated safety check: PassMIT
Phoenix Evalsgithub/awesome-copilot40k3 repos~1.1kAutomated safety check: PassApache-2.0
Langfuse Hello Worldjeremylongshore/tons-of-skills-marketplace2.8k1 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Phoenix LLM Observability

    Orchestra-Research/AI-Research-SKILLs

    Sets up Arize Phoenix to trace, evaluate and monitor LLM applications, with instrumentation for OpenAI, LangChain and LlamaIndex and a self-hosted server.

    13k GitHub starsUsed in 2 repos~2.9k tokens
    AI & LLM EngineeringAuto-check passed

  • Failproof AI SDK Integration

    FailproofAI/failproofai

    Helps instrument a custom Python or TypeScript agent to record events for Failproof AI, verify what gets written, and run an evaluator worker that scores the runs.

    5.3k GitHub stars~6k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed

  • Logfire Evals

    pydantic/skills

    Official

    Run offline Python (pydanticevals) or Node.js (logfire/evals) evaluations and review them in Logfire.

    140 GitHub stars~3.6k tokensUpdated 7 days ago
    AI & LLM EngineeringAuto-check passed

  • Phoenix Evals

    github/awesome-copilot

    Official

    Build and run evaluators for AI/LLM applications using Phoenix.

    40k GitHub starsUsed in 3 repos~1.1k tokens
    AI & LLM EngineeringAuto-check passed

  • Langfuse Hello World

    jeremylongshore/tons-of-skills-marketplace

    Create a minimal working Langfuse trace example. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub starsUsed in 1 repo~1.9k tokens
    AI & LLM EngineeringAuto-check passed

  • Langfuse Install Auth

    jeremylongshore/tons-of-skills-marketplace

    Install and configure Langfuse SDK authentication for LLM observability.

    2.8k GitHub starsUsed in 1 repo~1.7k tokens
    AI & LLM EngineeringAuto-check: notes

More from Arize-ai/phoenix

All 39 skills in this repo

  • Harbor Exec

    Arize-ai/phoenix

    A skill your agent uses when working with Harbor's harbor exec CLI workflow: compiling files, directories, or globs into Harbor tasks; running map jobs; configuring artifacts and existence-only…

    12k GitHub stars~909 tokensUpdated today
    Auto-check passed

  • Mintlify

    Arize-ai/phoenix

    Build and maintain documentation sites with Mintlify. An agent skill from Arize-ai/phoenix.

    12k GitHub starsUsed in 8 repos~3.4k tokens
    Auto-check passed

  • Phoenix Frontend

    Arize-ai/phoenix

    Frontend development guidelines for the Phoenix AI observability platform.

    12k GitHub stars~709 tokensUpdated today
    Auto-check passed

  • Phoenix Graphql

    Arize-ai/phoenix

    Write efficient GraphQL queries against the Phoenix API. An agent skill from Arize-ai/phoenix.

    12k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Phoenix Server

    Arize-ai/phoenix

    Backend development guide for the Phoenix AI observability platform (Strawberry GraphQL, SQLAlchemy async, FastAPI).

    12k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Phoenix Storybook

    Arize-ai/phoenix

    Conventions for creating, modifying, and reviewing production-faithful Storybook stories in the Phoenix frontend (js/app/stories, js/app/.storybook).

    12k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Phoenix Release Please

What does Phoenix Release Please do?

Bump the next release-please version for a Phoenix Python package (arize-phoenix, arize-phoenix-client, arize-phoenix-evals, arize-phoenix-otel) by opening a PR with a Release-As commit footer. Phoenix Release Please is an agent skill from Arize-ai/phoenix. Bump the next release-please version for a Phoenix Python package (arize-phoenix, arize-phoenix-client, arize-phoenix-evals, arize-phoenix-otel) by opening a PR with a Release-As commit footer.

When should I use Phoenix Release Please?

Phoenix Release Please fits situations like: the user asks to set the release-please version; force a 2.0.0 release; otherwise wants release-please to propose a specific version on its next run instead of the version it would pick from conventional commits.

How do I install Phoenix Release Please in Claude Code?

Run `npx skills add Arize-ai/phoenix --skill phoenix-release-please -a claude-code`. Or copy the skill folder (.agents/skills/phoenix-release-please in Arize-ai/phoenix) into .claude/skills/phoenix-release-please in your project. Claude Code loads it when a task matches its description.

How do I install Phoenix Release Please in Codex?

Run `npx skills add Arize-ai/phoenix --skill phoenix-release-please -a codex`. Or copy the skill folder (.agents/skills/phoenix-release-please in Arize-ai/phoenix) into .agents/skills/phoenix-release-please in your project. Codex loads it when a task matches its description.

Can I use Phoenix Release Please 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 Arize-ai/phoenix --skill phoenix-release-please -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/phoenix-release-please, .gemini/skills/phoenix-release-please, .github/skills/phoenix-release-please and .opencode/skills/phoenix-release-please in your project.

What does Phoenix Release Please need to run?

Going by SKILL.md and its folder, Phoenix Release Please needs the command-line tools its instructions call (git, jq and gh). Our summary lists: Python 3.

Does Phoenix Release Please access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Phoenix Release Please 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 Phoenix Release Please use?

Phoenix Release Please is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Phoenix Release Please use?

About 708 tokens (SKILL.md is roughly 2.8k 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 Phoenix Release Please?

Skills that share tags, products or a category with Phoenix Release Please: Phoenix LLM Observability (Orchestra-Research/AI-Research-SKILLs, 13k stars), Failproof AI SDK Integration (FailproofAI/failproofai, 5.3k stars), Logfire Evals (pydantic/skills, 140 stars) and Phoenix Evals (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phoenix Release Please?

Arize-ai (a GitHub organization) maintains it in Arize-ai/phoenix, which has 11,744 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 8, 2026.

Source: Arize-ai/phoenix on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.