Beyla
grafana/skills
Auto-instrument an application's HTTP / gRPC / DB traffic with Grafana Beyla eBPF — no code changes, no SDK, no restart.
A skill your agent uses when publishing prometheus-proxy to Maven Central, cutting a release, running a snapshot publish, or bumping the project version — covers the Maven Central coordinates, GPG…
Install Publishing Release
$ npx skills add pambrose/prometheus-proxy --skill publishing-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pambrose/prometheus-proxy publishing-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pambrose/prometheus-proxy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/publishing-release .claude/skills/publishing-release && rm -rf skills-srcUse ~/.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/
Install the "publishing-release" agent skill from https://github.com/pambrose/prometheus-proxy/tree/master/.claude/skills/publishing-release into .claude/skills/publishing-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pambrose/prometheus-proxy/tree/master/.claude/skills/publishing-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pambrose/prometheus-proxy --skill publishing-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pambrose/prometheus-proxy publishing-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pambrose/prometheus-proxy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/publishing-release .agents/skills/publishing-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "publishing-release" agent skill from https://github.com/pambrose/prometheus-proxy/tree/master/.claude/skills/publishing-release into .agents/skills/publishing-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pambrose/prometheus-proxy --skill publishing-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pambrose/prometheus-proxy publishing-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pambrose/prometheus-proxy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/publishing-release .cursor/skills/publishing-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "publishing-release" agent skill from https://github.com/pambrose/prometheus-proxy/tree/master/.claude/skills/publishing-release into .cursor/skills/publishing-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pambrose/prometheus-proxy.git --path .claude/skills/publishing-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pambrose/prometheus-proxy --skill publishing-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pambrose/prometheus-proxy publishing-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pambrose/prometheus-proxy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/publishing-release .gemini/skills/publishing-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "publishing-release" agent skill from https://github.com/pambrose/prometheus-proxy/tree/master/.claude/skills/publishing-release into .gemini/skills/publishing-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pambrose/prometheus-proxy publishing-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pambrose/prometheus-proxy --skill publishing-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pambrose/prometheus-proxy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/publishing-release .github/skills/publishing-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "publishing-release" agent skill from https://github.com/pambrose/prometheus-proxy/tree/master/.claude/skills/publishing-release into .github/skills/publishing-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pambrose/prometheus-proxy --skill publishing-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pambrose/prometheus-proxy publishing-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pambrose/prometheus-proxy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/publishing-release .opencode/skills/publishing-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "publishing-release" agent skill from https://github.com/pambrose/prometheus-proxy/tree/master/.claude/skills/publishing-release into .opencode/skills/publishing-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
publishing-release- GitHub stars
- 157
- Token cost
- ~506 tokens
- SKILL.md length
- 183 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when publishing prometheus-proxy to Maven Central, cutting a release, running a snapshot publish, or bumping the project version — covers the Maven Central coordinates, GPG…
- Publishing prometheus-proxy to Maven Central
- SKILL.md covers Publish targets and Bumping the version
- Calls make and git
- Cutting a release
What it does
Publishing Release is an agent skill from pambrose/prometheus-proxy. Use when publishing prometheus-proxy to Maven Central, cutting a release, running a snapshot publish, or bumping the project version — covers the Maven Central coordinates, GPG prerequisites, and the version-bump checklist.
Its SKILL.md is about 510 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 DevOps & Cloud, covering Monitoring and alerting. It works with Prometheus, Kotlin, gRPC and Docker. The licence is Apache-2.0.
When your agent uses it
- Publishing prometheus-proxy to Maven Central
- Cutting a release
- Running a snapshot publish
- Bumping the project version — covers the Maven Central coordinates
Example prompts
- “/publishing-release”
Requirements
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit bcaf988. 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:
makegit
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
Publishing Release loads about 506 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 183 words of instructions outside code blocks.
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 pambrose/prometheus-proxy at commit bcaf988, republished under its Apache-2.0 licence (© pambrose). 183 words, ~506 tokens.
Download SKILL.mdSave it as
.claude/skills/publishing-release/SKILL.md (or your agent's skills folder).- name
- publishing-release
- description
- Use when publishing prometheus-proxy to Maven Central, cutting a release, running a snapshot publish, or bumping the project version — covers the Maven Central coordinates, GPG prerequisites, and the version-bump checklist.
Publishing prometheus-proxy
Published to Maven Central as com.pambrose:prometheus-proxy. No JitPack.
Repository declarations are centralized in settings.gradle.kts via dependencyResolutionManagement(FAIL_ON_PROJECT_REPOS) and resolve solely from Maven Central.
Publish targets
Snapshot and Maven Central release Make targets (publish-snapshot, publish-maven-central) require GPG environment variables and a keychain password entry; make _check-gpg-env validates them up-front.
Bumping the version
When bumping the version, update version in gradle.properties and every hard-coded 4.2.0 literal (git grep -n for the outgoing version):
README.mdandllms.txt— Docker tag examples + Maven Central dependency block (README also gets a new release-summary paragraph at the top of New Features)etc/compose/proxy.yml— proxy and agent image tagscharts/prometheus-{proxy,agent}/Chart.yaml—versionandappVersion(the image tag the charts deploy)website/prometheus-proxy/docs/{getting-started,index,docker}.md— Docker pull/run examplessrc/test/kotlin/website/{DockerExamples,EmbeddedAgentExamples,KubernetesExamples}.txt— snippet sources the website's Docker, Embedded Agent, and Kubernetes pages include- this line, and step 2 of
docs/RELEASE.md
The Homebrew formulae need no edit for a bump: etc/homebrew/prometheus-{proxy,agent}.rb hold @VERSION@ / @SHA256@ placeholders that make homebrew-formulae fills in from the published GitHub release (step 9 of docs/RELEASE.md).
Leave historical mentions alone (CHANGELOG.md, RELEASE_NOTES.md, docs/archive/, the per-feature release annotations in llms.txt). The release flow itself is documented in docs/RELEASE.md.
© pambrose, 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 .claude/skills/publishing-release of pambrose/prometheus-proxy.
Open the folder on GitHubat commit bcaf988
Compare with similar skills
Publishing 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Publishing Release this skillpambrose/prometheus-proxy | 157 | — | ~506 | Automated safety check: Pass | Apache-2.0 | |
| Beylagrafana/skills | 281 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Kratos Developmentaide-family/moon | 253 | — | ~1.5k | Automated safety check: Pass | None | |
| Test Minecraft Exporterdirien/minecraft-prometheus-exporter | 142 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Dashboard Previewm4r1k/Eneru | 149 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Qdrant Advisorqdrant/skills | 254 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Kratos Development
aide-family/moon
Develops Go microservices with Kratos v2 following official design philosophy, DDD/Clean Architecture layout, Protobuf API, error/config/middleware patterns, and observability.
Test Minecraft Exporter
dirien/minecraft-prometheus-exporter
End-to-end docker-compose test harness for the minecraft-prometheus-exporter.
Dashboard Preview
m4r1k/Eneru
Visually verify Eneru browser-dashboard changes against a live daemon or audit an exact deployment.
- Official
Qdrant Advisor
qdrant/skills
Diagnose, troubleshoot, and advise on any Qdrant deployment by loading the latest official Qdrant skills live from skills.qdrant.tech.
Graft
m4r1k/Eneru
This repo is indexed by graft/. An agent skill from m4r1k/Eneru.
More from pambrose/prometheus-proxy
Docs Site
pambrose/prometheus-proxy
A skill your agent uses when editing, building, previewing, or deploying the prometheus-proxy documentation site under website/prometheus-proxy — covers the Zensical config, code-snippet resolution…
Related
Works with
Categories
Questions about Publishing Release
What does Publishing Release do?
A skill your agent uses when publishing prometheus-proxy to Maven Central, cutting a release, running a snapshot publish, or bumping the project version — covers the Maven Central coordinates, GPG…. Publishing Release is an agent skill from pambrose/prometheus-proxy. Use when publishing prometheus-proxy to Maven Central, cutting a release, running a snapshot publish, or bumping the project version — covers the Maven Central coordinates, GPG prerequisites, and the version-bump checklist.
When should I use Publishing Release?
Publishing Release fits situations like: publishing prometheus-proxy to Maven Central; cutting a release; running a snapshot publish; bumping the project version — covers the Maven Central coordinates.
How do I install Publishing Release in Claude Code?
Run `npx skills add pambrose/prometheus-proxy --skill publishing-release -a claude-code`. Or copy the skill folder (.claude/skills/publishing-release in pambrose/prometheus-proxy) into .claude/skills/publishing-release in your project. Claude Code loads it when a task matches its description.
How do I install Publishing Release in Codex?
Run `npx skills add pambrose/prometheus-proxy --skill publishing-release -a codex`. Or copy the skill folder (.claude/skills/publishing-release in pambrose/prometheus-proxy) into .agents/skills/publishing-release in your project. Codex loads it when a task matches its description.
Can I use Publishing 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 pambrose/prometheus-proxy --skill publishing-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/publishing-release, .gemini/skills/publishing-release, .github/skills/publishing-release and .opencode/skills/publishing-release in your project.
What does Publishing Release need to run?
Going by SKILL.md and its folder, Publishing Release needs the command-line tools its instructions call (make and git). Our summary lists: Docker.
Does Publishing 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 Publishing 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 Publishing Release use?
Publishing Release is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Publishing Release use?
About 506 tokens (SKILL.md is roughly 2k 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 Publishing Release?
Skills that share tags, products or a category with Publishing Release: Beyla (grafana/skills, 281 stars), Kratos Development (aide-family/moon, 253 stars), Test Minecraft Exporter (dirien/minecraft-prometheus-exporter, 142 stars) and Dashboard Preview (m4r1k/Eneru, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Publishing Release?
pambrose (a GitHub user) maintains it in pambrose/prometheus-proxy, which has 157 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.
Source: pambrose/prometheus-proxy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.