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

Release Audit

by mono in mono/SkiaSharp

Audit and coordinate one or more SkiaSharp release lines. An agent skill from mono/SkiaSharp.

MITAuto-check passedDevelopment

Install Release Audit

skills CLI
$ npx skills add mono/SkiaSharp --skill release-audit -a claude-code

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

GitHub CLI
$ gh skill install mono/SkiaSharp release-audit --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/mono/SkiaSharp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-audit .claude/skills/release-audit && 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
release-audit
GitHub stars
5.6k
Token cost
~1.4k tokens
SKILL.md length
681 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Audit and coordinate one or more SkiaSharp release lines. An agent skill from mono/SkiaSharp.

  • Works in 6 steps: Finish now — public packages with… → Resume publication — prepared branches… → Build blocked, running, or needing… → …
  • A maintainer asks what release work is done
  • SKILL.md covers Resolve requested lines, Run and aggregate, Investigate only exceptions and Mutating handoffs
  • Calls pwsh

What it does

Release Audit is an agent skill from mono/SkiaSharp. Audit and coordinate one or more SkiaSharp release lines. Use whenever a maintainer asks what release work is done, what should start/resume/finish, whether a range such as 4.150-4.155 or 4.15 is ready, or what blocks the next release action. Runs the repository audit command, aggregates its branch, internal build/BAR, NuGet, tag, GitHub Release, and upstream-sync evidence, investigates exceptional failures, and routes confirmed mutations to the owning release skills.

Its SKILL.md is about 1.4k 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. It works with GitHub. The repository describes itself as: SkiaSharp is a cross-platform 2D graphics API for .NET platforms based on Google's Skia Graphics Library. It provides a comprehensive 2D API that can be used across mobile… The licence is MIT.

When your agent uses it

  • A maintainer asks what release work is done
  • What should start/resume/finish
  • Whether a range such as 4.150-4.155
  • What blocks the next release action

Example prompts

  • “/release-audit”

Workflow steps

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

  1. Finish now — public packages with incomplete tags or Releases.
  2. Resume publication — prepared branches whose exact-tip build is green
  3. Build blocked, running, or needing review — missing, active, failed,
  4. Merge or synchronize before branching — upstream work and sync PRs.
  5. Start next releases — only Prepare actions emitted by the script.
  6. Unavailable or inconsistent checks — every exit 2, provenance

What it can do on your machine

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

    • pwsh

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

  • Network

    No URLs in SKILL.md.

    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

Release Audit loads about 1.4k tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 681 words of instructions outside code blocks.

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

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 mono/SkiaSharp at commit 51e2097, republished under its MIT licence (© mono). 681 words, ~1,416 tokens.

Download SKILL.mdSave it as .claude/skills/release-audit/SKILL.md (or your agent's skills folder).
name
release-audit
description
Audit and coordinate one or more SkiaSharp release lines. Use whenever a maintainer asks what release work is done, what should start/resume/finish, whether a range such as 4.150-4.155 or 4.15* is ready, or what blocks the next release action. Runs the repository audit command, aggregates its branch, internal build/BAR, NuGet, tag, GitHub Release, and upstream-sync evidence, investigates exceptional failures, and routes confirmed mutations to the owning release skills.

Release state coordinator

Use the repository command as the source of release facts:

powershell
pwsh ./scripts/infra/publishing/audit-release-state.ps1 -Version 4.152

The command is read-only and reports:

  • maintenance and specific release branches;
  • exact public NuGet provenance, tags, and GitHub Releases;
  • exact-tip internal skiasharp-package build status and BAR ID;
  • newer chrome/mN work and active sync PRs;
  • pre-transition main-line sync PRs left open after a servicing branch is cut;
  • pending next-milestone transitions; and
  • dependency-ordered Finish, build, publication, sync, and Prepare actions.

Use -Json when coordinating several lines. Exit 0 means no action, 1 means work or inconsistency remains, and 2 means a required check was unavailable. Never reinterpret exit 2 as healthy.

Resolve requested lines

Accept these natural selectors:

InputMeaning
4.152One exact major/minor line
4.150-4.155 or 4.150..4.155Inclusive numeric range
4.15*Matching discovered release lines plus current/pending main

For a numeric range, expand each minor. For a wildcard, discover unique lines from release branches, exact public NuGet versions, exact tags, current main, and the immediately following skia-sync/mN -> main transition. Do not invent empty lines beyond current or pending evidence.

Run and aggregate

Run independent line audits in parallel:

powershell
pwsh ./scripts/infra/publishing/audit-release-state.ps1 `
  -Version 4.152 `
  -Json

Do not manually repeat branch ordering, build selection, BAR parsing, upstream comparison, or action gating in the skill. Those deterministic rules belong to the PowerShell command and its shared modules. It prefers the newest succeeded BAR build on the exact branch commit; newer canceled or failed reruns are reported without displacing that build. A partially succeeded build with a BAR is reported for review, not marked ready.

Lead with:

LineCurrent stageExact-tip build / BARUpstream / syncNext action

Then group exact actions under:

  1. Finish now — public packages with incomplete tags or Releases.
  2. Resume publication — prepared branches whose exact-tip build is green and has one BAR ID.
  3. Build blocked, running, or needing review — missing, active, failed, canceled, BAR-less, or partially succeeded exact-tip builds without a succeeded BAR build.
  4. Merge or synchronize before branching — upstream work and sync PRs.
  5. Start next releases — only Prepare actions emitted by the script.
  6. Unavailable or inconsistent checks — every exit 2, provenance mismatch, ambiguous state, or unreachable service.

Always name and link every incomingPullRequest in the line summary, including draft PRs with BlocksRelease: false. Draft means not ready to merge, not absent: identify the review needed and do not describe the sync branch as already merged merely because its upstream comparison says current. For cross-repository sync, check the corresponding open mono/skia PR on the same sync branch and link the native PR before the parent SkiaSharp PR. Distinguish PR review from a release-cut blocker and from a newer upstream commit.

When a line has an already-cut branch plus newer maintenance/upstream work, state the sequence explicitly: publish the existing branch, land the sync, then rerun before cutting the following release.

Show full SKILL.md (222 more words)Show less

Investigate only exceptions

The command should provide enough information for normal release decisions. Use AI investigation only when it reports:

  • an unavailable internal pipeline or external service;
  • a failed or canceled exact-tip build without an earlier succeeded BAR build;
  • a partially succeeded BAR build offered for review;
  • several/missing BAR IDs;
  • mismatched branch, commit, tag, or public package provenance;
  • an incomplete cross-repository sync;
  • an ambiguous release identity; or
  • a workflow failure requiring logs or root-cause analysis.

Keep the original command output and exact IDs in the investigation. Do not replace unavailable evidence with an assumption.

Mutating handoffs

The audit and this skill remain read-only until the user asks to act:

  • Start: invoke release-branch; show the Prepare dry run and planned refs before push=true.
  • Publish packages: when explicitly requested, invoke release-publish to verify the exact producing Build/Tests runs and BAR, then queue the protected MAUI pipeline from chat. The pipeline's human approval remains mandatory; an audit never queues it automatically. The audit does not track already-queued MAUI publication runs, so check for one before dispatch.
  • Finish: invoke release-publish after exact packages are public; show the Finish workflow's read-only plan and obtain confirmation before push=true.
  • Sync Skia: follow update-skia and obtain confirmation before dispatch.

After any mutation completes, rerun the affected line. Never advance to the next stage based only on a successfully queued workflow.

© mono, 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/release-audit of mono/SkiaSharp.

Open the folder on GitHubat commit 51e2097

Compare with similar skills

Release Audit 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.

Release Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Audit this skillmono/SkiaSharp5.6k—~1.4kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Summarise Ecosystem Resultsastral-sh/ruff50k1 repos~2.2kAutomated safety check: PassMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Summarise Ecosystem Results

    astral-sh/ruff

    Official

    A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…

    50k GitHub starsUsed in 1 repo~2.2k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

More from mono/SkiaSharp

All 21 skills in this repo

  • Issue Fix

    mono/SkiaSharp

    Fix bugs in SkiaSharp C bindings. An agent skill from mono/SkiaSharp.

    5.6k GitHub stars~5.1k tokensUpdated today
    Auto-check passed

  • Issue Repro

    mono/SkiaSharp

    Reproduce a SkiaSharp issue systematically and capture structured reproduction results.

    5.6k GitHub stars~4.7k tokensUpdated today
    Auto-check passed

  • Issue Triage

    mono/SkiaSharp

    Triage a SkiaSharp GitHub issue or PR into structured JSON with classification (type, area, platform, severity), suggested response, automatable actions, and companion Markdown/HTML reports.

    5.6k GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Native Dependency Update

    mono/SkiaSharp

    Update native dependencies (libpng, libexpat, zlib, libwebp, harfbuzz, freetype, libjpeg-turbo, etc.) in SkiaSharp's Skia fork.

    5.6k GitHub stars~4.1k tokensUpdated today
    Auto-check passed

  • Review Skia Update

    mono/SkiaSharp

    Review a Skia upstream merge PR in mono/skia. An agent skill from mono/SkiaSharp.

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

  • Sample Scout

    mono/SkiaSharp

    Scout Skia GM (golden master) samples in the externals/skia submodule to find demos worth porting to the SkiaSharp Gallery.

    5.6k GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Release Audit

What does Release Audit do?

Audit and coordinate one or more SkiaSharp release lines. An agent skill from mono/SkiaSharp. Release Audit is an agent skill from mono/SkiaSharp. Audit and coordinate one or more SkiaSharp release lines.

When should I use Release Audit?

Release Audit fits situations like: A maintainer asks what release work is done; what should start/resume/finish; whether a range such as 4.150-4.155; what blocks the next release action.

How do I install Release Audit in Claude Code?

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

How do I install Release Audit in Codex?

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

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

What does Release Audit need to run?

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

Does Release Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

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

Release Audit 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 Release Audit use?

About 1.4k tokens (SKILL.md is roughly 5.7k 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 Release Audit?

Skills that share tags, products or a category with Release Audit: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Audit?

mono (a GitHub organization) maintains it in mono/SkiaSharp, which has 5,585 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

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