Agent skill

Release Milestones

by mono in mono/SkiaSharp

Reconcile shipped SkiaSharp pull requests and linked issues, maintain Chromium-derived release milestone dates, roll open work forward, and close shipped milestones with the repository-owned…

MITAuto-check passedProduct & Project Management

Install Release Milestones

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

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

GitHub CLI
$ gh skill install mono/SkiaSharp release-milestones --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-milestones .claude/skills/release-milestones && 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-milestones
GitHub stars
5.6k
Token cost
~546 tokens
SKILL.md length
168 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Reconcile shipped SkiaSharp pull requests and linked issues, maintain Chromium-derived release milestone dates, roll open work forward, and close shipped milestones with the repository-owned…

  • A maintainer asks to update
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Inspect release milestones
  • Milestone dates

What it does

Release Milestones is an agent skill from mono/SkiaSharp. Reconcile shipped SkiaSharp pull requests and linked issues, maintain Chromium-derived release milestone dates, roll open work forward, and close shipped milestones with the repository-owned PowerShell script. Use whenever a maintainer asks to update, repair, reconcile, advance, close, or inspect release milestones, milestone dates, or release assignments.

Its SKILL.md is about 550 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 Product & Project Management, covering Project management. It works with PowerShell. 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 to update
  • Inspect release milestones
  • Milestone dates
  • Release assignments

Example prompts

  • “/release-milestones”

What it can do on your machine

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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are powershell).

    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 Milestones loads about 546 tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 168 words of instructions outside code blocks.

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

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 cb51ed5, republished under its MIT licence (© mono). 168 words, ~546 tokens.

Download SKILL.mdSave it as .claude/skills/release-milestones/SKILL.md (or your agent's skills folder).
name
release-milestones
description
Reconcile shipped SkiaSharp pull requests and linked issues, maintain Chromium-derived release milestone dates, roll open work forward, and close shipped milestones with the repository-owned PowerShell script. Use whenever a maintainer asks to update, repair, reconcile, advance, close, or inspect release milestones, milestone dates, or release assignments.

Release Milestones

Release - Finish automatically runs both milestone operations after every successful preview, RC, stable, patch, or hotfix Finish. Its dry-run includes the milestone plan, and its push run verifies the exact immutable shipment tag before any milestone write.

Use Release - Milestones separately for diagnostics or repairs, with the needed independent operations selected and push disabled for a read-only run. After reviewing that output, dispatch again with push enabled, or run the two repository-owned scripts separately:

powershell
# Reconcile shipped assignments (read-only)
./scripts/infra/publishing/reconcile-release-assignments.ps1 `
  -Version 4.153.0

# Reconcile shipped assignments
./scripts/infra/publishing/reconcile-release-assignments.ps1 `
  -Version 4.153.0 `
  -Push

# Update dates, roll work forward, and close shipped milestones (read-only)
./scripts/infra/publishing/update-release-milestones.ps1

# Apply milestone updates
./scripts/infra/publishing/update-release-milestones.ps1 `
  -Push

Assignment reconciliation maps merged pull requests and linked issues to the release where they shipped. Milestone updates maintain upcoming Chromium-derived dates, move remaining open work to the next unshipped milestone, and close shipped milestones. When an exact shipped-release milestone is missing, reconciliation plans or creates it before assigning work.

Always run and present the selected read-only operation(s) before requesting confirmation for -Push. Missing shipped milestones are repaired automatically; missing tags, release boundaries, and ambiguous ownership still block remote reconciliation or closure. These scripts never create release branches, tags, packages, or GitHub Releases.

© 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-milestones of mono/SkiaSharp.

Open the folder on GitHubat commit cb51ed5

Compare with similar skills

Release Milestones 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 Milestones compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Milestones this skillmono/SkiaSharp5.6k—~546Automated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Supabase CLIfcakyon/claude-codex-settings1.2k—~1.5kAutomated safety check: NotesMIT
Roam Milestone PlanningCranot/roam-code517—~1.2kAutomated safety check: PassApache-2.0
Gh Read Inspectoreclipse-rdf4j/rdf4j420—~950Automated safety check: PassBSD-3-Clause
GitHub Project Management Swarmruvnet/agentic-flow8196 repos~7.1kAutomated safety check: PassNone

Similar skills

  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Supabase CLI

    fcakyon/claude-codex-settings

    This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase…

    1.2k GitHub stars~1.5k tokensUpdated yesterday
    Product & Project ManagementAuto-check: notes
  • Roam Milestone Planning

    Cranot/roam-code

    Define or revise a Roam product milestone and its engineering, adoption and offer-readiness sequence.

    517 GitHub stars~1.2k tokensUpdated 6 days ago
    Product & Project ManagementAuto-check passed
  • Gh Read Inspector

    eclipse-rdf4j/rdf4j

    Retrieve GitHub issues, pull requests, and milestones with read-only, whitelisted gh commands only.

    420 GitHub stars~950 tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Manages GitHub issues and project boards with swarm coordination: issue creation and triage, issue-to-task conversion, progress tracking and stale issue cleanup.

    819 GitHub starsUsed in 6 repos~7.1k tokens
    Product & Project ManagementAuto-check passed
  • Issue Triage

    superset-sh/superset

    Triage a GitHub issue into something actionable — reproduce the claim, find duplicates, judge severity, and apply labels, milestone, and assignee.

    15k GitHub stars~995 tokensUpdated today
    Product & Project ManagementAuto-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
  • 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

Questions about Release Milestones

What does Release Milestones do?

Reconcile shipped SkiaSharp pull requests and linked issues, maintain Chromium-derived release milestone dates, roll open work forward, and close shipped milestones with the repository-owned…. Release Milestones is an agent skill from mono/SkiaSharp. Reconcile shipped SkiaSharp pull requests and linked issues, maintain Chromium-derived release milestone dates, roll open work forward, and close shipped milestones with the repository-owned PowerShell script.

When should I use Release Milestones?

Release Milestones fits situations like: A maintainer asks to update; inspect release milestones; milestone dates; release assignments.

How do I install Release Milestones in Claude Code?

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

How do I install Release Milestones in Codex?

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

Can I use Release Milestones 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-milestones -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-milestones, .gemini/skills/release-milestones, .github/skills/release-milestones and .opencode/skills/release-milestones in your project.

What does Release Milestones need to run?

SKILL.md names no scripts, command-line tools or credentials: Release Milestones is instructions for the agent only.

Does Release Milestones 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 Milestones 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 Milestones use?

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

About 546 tokens (SKILL.md is roughly 2.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 Release Milestones?

Skills that share tags, products or a category with Release Milestones: CCPM Project Management (automazeio/ccpm, 8.4k stars), Supabase CLI (fcakyon/claude-codex-settings, 1.2k stars), Roam Milestone Planning (Cranot/roam-code, 517 stars) and Gh Read Inspector (eclipse-rdf4j/rdf4j, 420 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Milestones?

mono (a GitHub organization) maintains it in mono/SkiaSharp, which has 5,587 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 9, 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.