How do I install the Paradise Release skill?

Run npx skillmds@latest add paradiseengine/paradise-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Paradise Release safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Paradise Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Paradise Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Paradise Release?

ParadiseEngine (@paradiseengine) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Paradise Release by paradiseengine — Agent Skill

Name: Paradise Release
Rating: 4.666666666666667 (3 reviews)
Author: ParadiseEngine

File contents

Release ParadiseEngine

Complete the release and consumer updates requested by the user. Loading this skill does not authorize merging, pushing, tagging, or updating unrelated consumers.

Release the selected revision

Confirm the target repository, requested version, revision, and any PR's current required checks. Use explicit PR numbers and SHAs; do not infer them from a branch in a deferred command.
ParadiseEngine releases are tag-driven: push an annotated vX.Y.Z tag at the intended commit. publish-nuget.yml derives the package version from the tag. Do not change the default <Version> or create a version-bump PR just to release.
If merging is included, satisfy the branch policies first. Retarget downstream stacked PRs before deleting their base branch. Preserve unrelated work when updating the local checkout.
A new packable project must appear in the publish workflow's project list. Inspect that list when the release adds packages; a green job alone cannot prove an omitted package shipped.

Establish availability

Find the workflow run for the exact tag and revision, then inspect its conclusion and package push results. Poll only the required package indexes while indexing is pending. A green publish can precede NuGet availability by several minutes; do not repeatedly push or move a released tag. Diagnose a failed or stalled run and report the concrete blocker if it cannot be resolved within the authorized release. Published NuGet versions cannot be reused.

Prove availability with a fresh package-mode restore using an empty NUGET_PACKAGES directory. --no-cache alone still uses the local package cache. Check restore success before using any --no-build test or runtime command.

Update requested consumers

Update the consumer's shared ParadiseVersion pin and relevant CLI installation examples. Keep engine package pins aligned; Paradise.Godot.Editor has a separate addon version line. Build and run affected checks in package mode (-p:ParadiseUseEngineSource=false). If the task includes consumer publication, continue through its requested commit, push, PR, or CI result.

Report the release tag and revision, publishing result, fresh-restore evidence, and consumer status. Record memory only under the user's applicable memory instructions.

---name: paradise-releasedescription: Publish a requested ParadiseEngine release and update the specified consumers after NuGet becomes available.---# Release ParadiseEngineComplete the release and consumer updates requested by the user. Loading this skill does notauthorize merging, pushing, tagging, or updating unrelated consumers.## Release the selected revision- Confirm the target repository, requested version, revision, and any PR's current required checks. Use explicit PR numbers and SHAs; do not infer them from a branch in a deferred command.- ParadiseEngine releases are tag-driven: push an annotated `vX.Y.Z` tag at the intended commit. `publish-nuget.yml` derives the package version from the tag. Do not change the default `<Version>` or create a version-bump PR just to release.- If merging is included, satisfy the branch policies first. Retarget downstream stacked PRs before deleting their base branch. Preserve unrelated work when updating the local checkout.- A new packable project must appear in the publish workflow's project list. Inspect that list when the release adds packages; a green job alone cannot prove an omitted package shipped.## Establish availabilityFind the workflow run for the exact tag and revision, then inspect its conclusion and packagepush results. Poll only the required package indexes while indexing is pending. A green publishcan precede NuGet availability by several minutes; do not repeatedly push or move a released tag.Diagnose a failed or stalled run and report the concrete blocker if it cannot be resolved withinthe authorized release. Published NuGet versions cannot be reused.Prove availability with a fresh package-mode restore using an empty `NUGET_PACKAGES` directory.`--no-cache` alone still uses the local package cache. Check restore success before using any`--no-build` test or runtime command.## Update requested consumersUpdate the consumer's shared `ParadiseVersion` pin and relevant CLI installation examples.Keep engine package pins aligned; `Paradise.Godot.Editor` has a separate addon version line.Build and run affected checks in package mode (`-p:ParadiseUseEngineSource=false`). If the taskincludes consumer publication, continue through its requested commit, push, PR, or CI result.Report the release tag and revision, publishing result, fresh-restore evidence, and consumerstatus. Record memory only under the user's applicable memory instructions.

Frequently asked questions

Paradise Release