React Native Best Practices
vercel-labs/openreview
A prioritized rule set for React Native and Expo apps covering list performance, animation, navigation, UI patterns, state, rendering, monorepos and configuration.
Publish SkiaSharp release packages to NuGet.org from chat and finish public releases.
Install Release Publish
$ npx skills add mono/SkiaSharp --skill release-publish -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mono/SkiaSharp release-publish --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/mono/SkiaSharp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-publish .claude/skills/release-publish && 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 "release-publish" agent skill from https://github.com/mono/SkiaSharp/tree/main/.agents/skills/release-publish into .claude/skills/release-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-publish", 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/mono/SkiaSharp/tree/main/.agents/skills/release-publishType 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 mono/SkiaSharp --skill release-publish -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mono/SkiaSharp release-publish --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mono/SkiaSharp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release-publish .agents/skills/release-publish && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-publish" agent skill from https://github.com/mono/SkiaSharp/tree/main/.agents/skills/release-publish into .agents/skills/release-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-publish", 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 mono/SkiaSharp --skill release-publish -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mono/SkiaSharp release-publish --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mono/SkiaSharp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release-publish .cursor/skills/release-publish && 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 "release-publish" agent skill from https://github.com/mono/SkiaSharp/tree/main/.agents/skills/release-publish into .cursor/skills/release-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-publish", 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/mono/SkiaSharp.git --path .agents/skills/release-publish--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 mono/SkiaSharp --skill release-publish -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mono/SkiaSharp release-publish --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mono/SkiaSharp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release-publish .gemini/skills/release-publish && 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 "release-publish" agent skill from https://github.com/mono/SkiaSharp/tree/main/.agents/skills/release-publish into .gemini/skills/release-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-publish", 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 mono/SkiaSharp release-publishInstalls 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 mono/SkiaSharp --skill release-publish -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mono/SkiaSharp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release-publish .github/skills/release-publish && 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 "release-publish" agent skill from https://github.com/mono/SkiaSharp/tree/main/.agents/skills/release-publish into .github/skills/release-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-publish", 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 mono/SkiaSharp --skill release-publish -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mono/SkiaSharp release-publish --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mono/SkiaSharp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release-publish .opencode/skills/release-publish && 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 "release-publish" agent skill from https://github.com/mono/SkiaSharp/tree/main/.agents/skills/release-publish into .opencode/skills/release-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-publish", 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
release-publish- GitHub stars
- 5.6k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 492 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Publish SkiaSharp release packages to NuGet.org from chat and finish public releases.
- Works in 3 steps: Run audit-release-state.ps1 -Version A.B… → Check the complete public package set… → Require the dotnet-maui-release (1445)…
- A maintainer says push the packages
- SKILL.md covers Push the packages and Finish after the packages are…
- Calls gh and az; reaches dev.azure.com
What it does
Release Publish is an agent skill from mono/SkiaSharp. Publish SkiaSharp release packages to NuGet.org from chat and finish public releases. Use when a maintainer says "push the packages", "publish the BAR", "resume publication", "finalize X", "tag X", or "finish release X". Queue the protected MAUI pipeline only on explicit request; after exact packages are public, use the SkiaSharp Release - Finish workflow with a separate confirmation.
Its SKILL.md is about 1.2k 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 Mobile, covering Cross-platform mobile apps. 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 says push the packages
- Publish the BAR
- Resume publication
- Finish release X
Example prompts
- “push the packages”
- “publish the BAR”
- “resume publication”
- “/release-publish”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Run audit-release-state.ps1 -Version A.B -Json for the requested
- Check the complete public package set and existing
- Require the dotnet-maui-release (1445) pipeline to default to
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
Shell commands in SKILL.md call:
ghaz
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
dev.azure.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
Release Publish loads about 1.2k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 492 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 mono/SkiaSharp at commit cb51ed5, republished under its MIT licence (© mono). 492 words, ~1,228 tokens.
Download SKILL.mdSave it as
.claude/skills/release-publish/SKILL.md (or your agent's skills folder).- name
- release-publish
- description
- Publish SkiaSharp release packages to NuGet.org from chat and finish public releases. Use when a maintainer says "push the packages", "publish the BAR", "resume publication", "finalize X", "tag X", or "finish release X". Queue the protected MAUI pipeline only on explicit request; after exact packages are public, use the SkiaSharp Release - Finish workflow with a separate confirmation.
Release Publish
Use this skill for two separate chat requests: "push the packages" queues the MAUI publication pipeline; "finish the release" dispatches the SkiaSharp Finish workflow after the packages are public. Neither runs automatically after Prepare, Build/Tests, or the other operation.
Push the packages
Before triggering:
- Run
audit-release-state.ps1 -Version A.B -Jsonfor the requestedrelease/<identity>. Require its exact-tipskiasharp-package (1642)build to have succeeded with one BAR, and the resource-triggeredskiasharp-tests (1630)run to have succeeded for the same branch, commit and build number with a matchingtriggerInfo.pipelineId. The producing Build/Tests runs and BAR are the release-validation evidence; do not require a separate local approval report. Use that SkiaSharp commit, not the maintenance tip or mono/skia SHA. - Check the complete public package set and existing
dotnet-maui-release (1445)runs for that commit (templateParameters.commitHash). Monitor an existing run instead of queueing another; if fully public, verify provenance and use the Finish path only on a separate request. Stop on mismatched evidence. - Require the
dotnet-maui-release (1445)pipeline to default torefs/heads/mainand the internal MAUI mirror to contain the merged SkiaSharp release support. Wait if the mirror is behind; never use the old feature branch.
Queue dotnet-maui-release (1445) on its verified default MAUI main tip
only on explicit request:
az pipelines run \
--organization https://dev.azure.com/dnceng --project internal --id 1445 \
--parameters \
ghOwner=mono \
ghRepo=SkiaSharp \
commitHash=<exact-SkiaSharp-release-commit> \
pushWorkloadSet=false \
pushNugetOrg=true \
pushPackages=true \
nugetIncludeFilters=skip \
nugetExcludeFilters=skip \
--output jsonThe pipeline's default branch selects the current MAUI main tip;
commitHash remains the exact SkiaSharp BAR commit. The real run prepares
packages and pauses at ManualValidation, so no separate dry run is required.
After triggering:
- Read back the run's MAUI ref/SHA and parameters. Require
refs/heads/main, the requested SkiaSharp commit and flags, and a MAUI SHA containing release support; stop on a mismatch without retrying. - Match
NuGetReleaseAuditBAR, repository, commit and selected/staged package identities to the release record. Present it for humanManualValidation; the approver confirms package ownership and quota. Preparation alone is not approval. - Monitor that run after approval and independently verify every staged shipping ID/version on NuGet.org. On failure or partial publication, preserve evidence; do not automatically requeue or run Finish.
Show full SKILL.md (158 more words)Show less
Finish after the packages are public
Once the complete exact package set is public, use Release - Finish on
main, first with push=false to inspect the read-only plan. Resolve an
abbreviated prerelease identity to one exact public version; stop if ambiguous.
Present the source commit, exact tag, release title, support updates and
milestone changes to the user and obtain separate confirmation before
dispatching the same inputs with push=true:
gh workflow run release-finish.yml --repo mono/SkiaSharp --ref main \
-f version=4.153.0-preview.1 -f push=false
# After the plan is reviewed and separately approved:
gh workflow run release-finish.yml --repo mono/SkiaSharp --ref main \
-f version=4.153.0-preview.1 -f push=trueInspect both workflow runs; do not treat dispatch as success. Finish verifies the public package's branch and commit, publishes the exact tag and GitHub Release, and coordinates support, release notes, and milestones. Rerun the read-only audit afterward. Never move a tag or replace a public package.
Local Finish fallback
Only when the GitHub workflow is unavailable or local execution is explicitly requested, use the repository-owned Finish script:
./scripts/infra/publishing/finish-release.ps1 -Version 4.153.0-preview.1 -Mode DryRun
# After reviewing the plan and receiving confirmation:
./scripts/infra/publishing/finish-release.ps1 -Version 4.153.0-preview.1 -Mode PushLocal Finish does not replace the protected MAUI package pipeline or its human NuGet approval. Do not use it to bypass a failed 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-publish of mono/SkiaSharp.
Open the folder on GitHubat commit cb51ed5
Compare with similar skills
Release Publish 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 |
|---|---|---|---|---|---|---|
| Release Publish this skillmono/SkiaSharp | 5.6k | — | ~1.2k | Automated safety check: Pass | MIT | |
| React Native Best Practicesvercel-labs/openreview | 1.7k | 17 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Compose Multiplatform Patternsmonta-app/ocpp-emulator | 180 | 5 repos | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Creating Reanimated Animationsgluestack/gluestack-ui | 5.3k | — | ~2.4k | Automated safety check: Pass | None | |
| Uni-app Components and APIsfeige996/unibest | 2.3k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Add Flutter Docusaurus Localematthiasn/lotti | 1.2k | — | ~1.2k | Automated safety check: Pass | GPL-3.0 |
Similar skills
- Official
Compose Multiplatform Patterns
monta-app/ocpp-emulator
Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.
Creating Reanimated Animations
gluestack/gluestack-ui
Generate React Native Reanimated animation code for React Native apps.
Uni-app Components and APIs
feige996/unibest
Gives per-component and per-API examples, reference specs and compatibility notes for building cross-platform uni-app apps, mirroring the official documentation.
Add Flutter Docusaurus Locale
matthiasn/lotti
Add, complete, or audit a locale across a Flutter application's ARB catalogs and a localized Docusaurus manual, including generated localization code, locale selectors, native platform declarations…
Jetpack Compose Expert
aldefy/compose-skill
Guides Jetpack Compose and Compose Multiplatform work across Android, Desktop, iOS and web, plus Android TV, Material 3 motion, paging, navigation and design-to-code.
More from mono/SkiaSharp
All 21 skills in this repoIssue Fix
mono/SkiaSharp
Fix bugs in SkiaSharp C bindings. An agent skill from mono/SkiaSharp.
Issue Repro
mono/SkiaSharp
Reproduce a SkiaSharp issue systematically and capture structured reproduction results.
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.
Native Dependency Update
mono/SkiaSharp
Update native dependencies (libpng, libexpat, zlib, libwebp, harfbuzz, freetype, libjpeg-turbo, etc.) in SkiaSharp's Skia fork.
Review Skia Update
mono/SkiaSharp
Review a Skia upstream merge PR in mono/skia. An agent skill from mono/SkiaSharp.
Sample Scout
mono/SkiaSharp
Scout Skia GM (golden master) samples in the externals/skia submodule to find demos worth porting to the SkiaSharp Gallery.
Related
Categories
Questions about Release Publish
What does Release Publish do?
Publish SkiaSharp release packages to NuGet.org from chat and finish public releases. Release Publish is an agent skill from mono/SkiaSharp.org from chat and finish public releases.
When should I use Release Publish?
Release Publish fits situations like: A maintainer says push the packages; publish the BAR; resume publication; finish release X.
How do I install Release Publish in Claude Code?
Run `npx skills add mono/SkiaSharp --skill release-publish -a claude-code`. Or copy the skill folder (.agents/skills/release-publish in mono/SkiaSharp) into .claude/skills/release-publish in your project. Claude Code loads it when a task matches its description.
How do I install Release Publish in Codex?
Run `npx skills add mono/SkiaSharp --skill release-publish -a codex`. Or copy the skill folder (.agents/skills/release-publish in mono/SkiaSharp) into .agents/skills/release-publish in your project. Codex loads it when a task matches its description.
Can I use Release Publish 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-publish -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-publish, .gemini/skills/release-publish, .github/skills/release-publish and .opencode/skills/release-publish in your project.
What does Release Publish need to run?
Going by SKILL.md and its folder, Release Publish needs the command-line tools its instructions call (gh and az).
Does Release Publish access the network?
SKILL.md names 1 domain. In commands or code: dev.azure.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Release Publish 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 Publish use?
Release Publish 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 Publish use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Publish?
Skills that share tags, products or a category with Release Publish: React Native Best Practices (vercel-labs/openreview, 1.7k stars), Compose Multiplatform Patterns (monta-app/ocpp-emulator, 180 stars), Creating Reanimated Animations (gluestack/gluestack-ui, 5.3k stars) and Uni-app Components and APIs (feige996/unibest, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Publish?
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.