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

Jacky Creator Release

by Jackywxsz in Jackywxsz/DSH-Creator

Run and strongly accept Jacky Creator's branch-to-release workflow: verify feature branches, merge approved changes, synchronize every version surface, build one immutable artifact, publish…

MITAuto-check passed

Install Jacky Creator Release

skills CLI
$ npx skills add Jackywxsz/DSH-Creator --skill jacky-creator-release -a claude-code

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

GitHub CLI
$ gh skill install Jackywxsz/DSH-Creator jacky-creator-release --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/Jackywxsz/DSH-Creator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/jacky-creator-release .claude/skills/jacky-creator-release && 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
jacky-creator-release
GitHub stars
110
Token cost
~1.1k tokens
SKILL.md length
550 words
Files
2 (incl. references)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Run and strongly accept Jacky Creator's branch-to-release workflow: verify feature branches, merge approved changes, synchronize every version surface, build one immutable artifact, publish…

  • Works in 9 steps: Freeze the candidate. On the feature… → Run pnpm release:check before merging… → Merge the approved branch into main only… → …
  • Finishing a release
  • SKILL.md covers Completion Contract, Workflow and Release Invariants
  • Calls pnpm, git and npm

What it does

Jacky Creator Release is an agent skill from Jackywxsz/DSH-Creator. Run and strongly accept Jacky Creator's branch-to-release workflow: verify feature branches, merge approved changes, synchronize every version surface, build one immutable artifact, publish GitHub/npm/marketplace surfaces, and prove the installed result. Use when preparing or finishing a release, recovering a failed publication, checking whether a release is really live, or applying reusable last-mile release controls to another project.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/last-mile-release.md`).

It works with npm, GitHub, DeepSeek and pnpm. The repository describes itself as: Jacky Creator：面向内容创作者的 DeepSeek Harness 本地内容与运营工作台. The licence is MIT.

When your agent uses it

  • Finishing a release
  • Recovering a failed publication
  • Checking whether a release is really live
  • Applying reusable last-mile release controls to another project

Example prompts

  • “/jacky-creator-release”

Workflow steps

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

  1. Freeze the candidate. On the feature branch, run git status --short --branch -uall, fetch the live target remote, inspect the diff from…
  2. Run pnpm release:check before merging and stop on any failure. Preserve unrelated worktree changes; never reset or stash user files…
  3. Merge the approved branch into main only after re-reading the candidate SHA, target SHA, worktree status, and CI. Resolve conflicts…
  4. Choose the lane and version. Beta releases use the next 0.1.0-beta.N; stable releases require the documented cross-platform evidence…
  5. Build once with pnpm check, run pnpm release:check, and create the final tarball from that verified tree. Inspect npm pack --dry-run…
  6. Preflight identities, permissions, transports, exact artifact paths, and destination state before the first public write. Use real…
  7. Commit only intended files and push main. Create an annotated or signed version tag, then the matching GitHub prerelease and Release…
  8. Strongly accept the release by re-reading live GitHub branch/tag/Release data, CI, npm metadata and integrity, marketplace PR…
  9. Report a final ledger for source, tag, Release notes, Release asset, npm, README/docs, marketplace PR, marketplace live entry, CI, and…

What it can do on your machine

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

    • pnpm
    • git
    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, git and npm, 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

Jacky Creator Release loads about 1.1k tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 116 tokens; SKILL.md has 550 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~116
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.6k

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 Jackywxsz/DSH-Creator at commit 5018193, republished under its MIT licence (© Jackywxsz). 550 words, ~1,131 tokens.

Download SKILL.mdSave it as .claude/skills/jacky-creator-release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
jacky-creator-release
description
Run and strongly accept Jacky Creator's branch-to-release workflow: verify feature branches, merge approved changes, synchronize every version surface, build one immutable artifact, publish GitHub/npm/marketplace surfaces, and prove the installed result. Use when preparing or finishing a release, recovering a failed publication, checking whether a release is really live, or applying reusable last-mile release controls to another project.

Jacky Creator Release

Completion Contract

A release is complete only when every applicable surface is recorded as done, not applicable, or blocked with owner and next action. A successful source push, GitHub Release, npm publish, or marketplace PR alone is not a completed release.

Before any public publish, marketplace update, or recovery from a failed release command, read references/last-mile-release.md. Apply its generic control plane first, then the project mapping below.

Workflow

  1. Freeze the candidate. On the feature branch, run git status --short --branch -uall, fetch the live target remote, inspect the diff from the latest release tag, and run pnpm check. Never infer remote state only from a cached tracking ref.
  2. Run pnpm release:check before merging and stop on any failure. Preserve unrelated worktree changes; never reset or stash user files without authorization.
  3. Merge the approved branch into main only after re-reading the candidate SHA, target SHA, worktree status, and CI. Resolve conflicts explicitly and rerun all gates after the merge.
  4. Choose the lane and version. Beta releases use the next 0.1.0-beta.N; stable releases require the documented cross-platform evidence. Search the whole repository for stale versioned URLs and update every current user-facing surface, including package.json, README.md, docs/installation.md, docs/distribution.md, implementation/status docs, tests, and CHANGELOG.md.
  5. Build once with pnpm check, run pnpm release:check, and create the final tarball from that verified tree. Inspect npm pack --dry-run --ignore-scripts --json; verify runtime files, user docs, Hero assets, and absence of credentials, caches, private paths, or internal-only files.
  6. Preflight identities, permissions, transports, exact artifact paths, and destination state before the first public write. Use real resolved paths, never documentation placeholders. For fork-based marketplace work, branch from the live upstream default branch and verify that the chosen Git transport can update workflow-bearing history.
  7. Commit only intended files and push main. Create an annotated or signed version tag, then the matching GitHub prerelease and Release asset. Publish the exact same tarball to npm. Update awesome-dsh-plugin/data/plugins/Jackywxsz__DSH-Creator.yml with the exact Release tarball URL.
  8. Strongly accept the release by re-reading live GitHub branch/tag/Release data, CI, npm metadata and integrity, marketplace PR diff/checks/merge state/live entry, documentation links, and a clean-profile install/restart/upgrade/uninstall smoke test. Compare the downloaded GitHub and npm tarballs byte-for-byte.
  9. Report a final ledger for source, tag, Release notes, Release asset, npm, README/docs, marketplace PR, marketplace live entry, CI, and installed runtime. Do not say “发布完成” while any required row is merely submitted, waiting, or unverified.
Show full SKILL.md (145 more words)Show less

Release Invariants

  • GitHub tag, Release asset, npm version, README links, installation docs, distribution docs, and marketplace tarball must all name the same version.
  • The version tag must resolve to an annotated or signed tag object, not a lightweight commit ref.
  • Build the published archive from the verified tree. Include prebuilt Host, Client, Typert, Bundle Patch, user documentation, and Hero assets.
  • GitHub Release and npm must distribute the same bytes and therefore the same cryptographic digest.
  • Never publish a dirty tree, floating source install, stable artifact from beta evidence, or a package containing local paths, credentials, caches, screenshots, or user content.
  • Web login, passkey enrollment, CLI login, OTP, registry publish permission, and Git push permission are separate capabilities. Prove the capability required by the next command without exposing credentials.
  • Public publishing is irreversible. Require explicit authorization for push, tag, GitHub Release, npm publish, and marketplace updates.

© Jackywxsz, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/jacky-creator-release of Jackywxsz/DSH-Creator.

  • SKILL.md
  • references/last-mile-release.md

Open the folder on GitHubat commit 5018193

Compare with similar skills

Jacky Creator 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.

Jacky Creator Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jacky Creator Release this skillJackywxsz/DSH-Creator110—~1.1kAutomated safety check: PassMIT
OpenGUI Installer for DSHCore-Mate/OpenGUI1.8k—~1.1kAutomated safety check: PassCustom licence
Dsh Web UI Releaseningbainb/deepseek-harness-desktop789—~1.4kAutomated safety check: WarnBSD-3-Clause
Plugin ReleaseNanmiCoder/dsh-auto-mode1641 repos~1.6kAutomated safety check: WarnMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Ant Design Mobile Releaseant-design/ant-design-mobile12k—~497Automated safety check: PassMIT

Similar skills

  • OpenGUI Installer for DSH

    Core-Mate/OpenGUI

    Installs and verifies the latest stable OpenGUI release in a DeepSeek Harness web profile on macOS without disturbing existing plugins or settings.

    1.8k GitHub stars~1.1k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed

  • Dsh Web UI Release

    ningbainb/deepseek-harness-desktop

    Release and publish the dsh-web-ui monorepo (DSH Web GUI plugin family + skin collection) — bump all packages to one unified version, commit and tag, push the vX.Y.Z tag that triggers the GitHub…

    789 GitHub stars~1.4k tokensUpdated 4 days ago
    DevelopmentAuto-check: warnings

  • Plugin Release

    NanmiCoder/dsh-auto-mode

    Package, publish, and distribute DeepSeek Harness (DSH) plugins — npm pack artifact validation, GitHub/npm/hub release-track selection, tarball overrides installs for the unpublished cohort…

    164 GitHub starsUsed in 1 repo~1.6k tokens
    DevOps & CloudAuto-check: warnings

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Ant Design Mobile Release

    ant-design/ant-design-mobile

    Prepares an npm release of ant-design-mobile up to the version commit, then tags and publishes the GitHub Release after you run the publish command yourself.

    12k GitHub stars~497 tokensUpdated 26 days ago
    DevelopmentAuto-check passed

  • ZCF Release Automation

    UfoMiao/zcf

    Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

Works with

Questions about Jacky Creator Release

What does Jacky Creator Release do?

Run and strongly accept Jacky Creator's branch-to-release workflow: verify feature branches, merge approved changes, synchronize every version surface, build one immutable artifact, publish…. Jacky Creator Release is an agent skill from Jackywxsz/DSH-Creator. Run and strongly accept Jacky Creator's branch-to-release workflow: verify feature branches, merge approved changes, synchronize every version surface, build one immutable artifact, publish GitHub/npm/marketplace surfaces, and prove the installed result.

When should I use Jacky Creator Release?

Jacky Creator Release fits situations like: finishing a release; recovering a failed publication; checking whether a release is really live; applying reusable last-mile release controls to another project.

How do I install Jacky Creator Release in Claude Code?

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

How do I install Jacky Creator Release in Codex?

Run `npx skills add Jackywxsz/DSH-Creator --skill jacky-creator-release -a codex`. Or copy the skill folder (.agents/skills/jacky-creator-release in Jackywxsz/DSH-Creator) into .agents/skills/jacky-creator-release in your project. Codex loads it when a task matches its description.

Can I use Jacky Creator 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 Jackywxsz/DSH-Creator --skill jacky-creator-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/jacky-creator-release, .gemini/skills/jacky-creator-release, .github/skills/jacky-creator-release and .opencode/skills/jacky-creator-release in your project.

What does Jacky Creator Release need to run?

Going by SKILL.md and its folder, Jacky Creator Release needs the command-line tools its instructions call (pnpm, git and npm).

Does Jacky Creator Release access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

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

Jacky Creator Release 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 Jacky Creator Release use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Jacky Creator Release?

Skills that share tags, products or a category with Jacky Creator Release: OpenGUI Installer for DSH (Core-Mate/OpenGUI, 1.8k stars), Dsh Web UI Release (ningbainb/deepseek-harness-desktop, 789 stars), Plugin Release (NanmiCoder/dsh-auto-mode, 164 stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jacky Creator Release?

Jackywxsz (a GitHub user) maintains it in Jackywxsz/DSH-Creator, which has 110 GitHub stars. The repository was last updated on October 9, 2026.

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