Ccb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
Automate npm package publishing via GitHub Actions for single-package repos and independent monorepo packages, including bumpp version tags, GitHub release notes, trusted publishing, provenance, and…
Install Automate npm Release
$ npx skills add jd-solanki/slidev-theme-dracula --skill automate-npm-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jd-solanki/slidev-theme-dracula automate-npm-release --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/jd-solanki/slidev-theme-dracula.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.ai/skills/automate-npm-release .claude/skills/automate-npm-release && 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 "automate-npm-release" agent skill from https://github.com/jd-solanki/slidev-theme-dracula/tree/main/.ai/skills/automate-npm-release into .claude/skills/automate-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-npm-release", 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/jd-solanki/slidev-theme-dracula/tree/main/.ai/skills/automate-npm-releaseType 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 jd-solanki/slidev-theme-dracula --skill automate-npm-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jd-solanki/slidev-theme-dracula automate-npm-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jd-solanki/slidev-theme-dracula.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.ai/skills/automate-npm-release .agents/skills/automate-npm-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "automate-npm-release" agent skill from https://github.com/jd-solanki/slidev-theme-dracula/tree/main/.ai/skills/automate-npm-release into .agents/skills/automate-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-npm-release", 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 jd-solanki/slidev-theme-dracula --skill automate-npm-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jd-solanki/slidev-theme-dracula automate-npm-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jd-solanki/slidev-theme-dracula.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.ai/skills/automate-npm-release .cursor/skills/automate-npm-release && 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 "automate-npm-release" agent skill from https://github.com/jd-solanki/slidev-theme-dracula/tree/main/.ai/skills/automate-npm-release into .cursor/skills/automate-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-npm-release", 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/jd-solanki/slidev-theme-dracula.git --path .ai/skills/automate-npm-release--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 jd-solanki/slidev-theme-dracula --skill automate-npm-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jd-solanki/slidev-theme-dracula automate-npm-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jd-solanki/slidev-theme-dracula.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.ai/skills/automate-npm-release .gemini/skills/automate-npm-release && 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 "automate-npm-release" agent skill from https://github.com/jd-solanki/slidev-theme-dracula/tree/main/.ai/skills/automate-npm-release into .gemini/skills/automate-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-npm-release", 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 jd-solanki/slidev-theme-dracula automate-npm-releaseInstalls 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 jd-solanki/slidev-theme-dracula --skill automate-npm-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jd-solanki/slidev-theme-dracula.git skills-src && mkdir -p .github/skills && cp -r skills-src/.ai/skills/automate-npm-release .github/skills/automate-npm-release && 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 "automate-npm-release" agent skill from https://github.com/jd-solanki/slidev-theme-dracula/tree/main/.ai/skills/automate-npm-release into .github/skills/automate-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-npm-release", 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 jd-solanki/slidev-theme-dracula --skill automate-npm-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jd-solanki/slidev-theme-dracula automate-npm-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jd-solanki/slidev-theme-dracula.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.ai/skills/automate-npm-release .opencode/skills/automate-npm-release && 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 "automate-npm-release" agent skill from https://github.com/jd-solanki/slidev-theme-dracula/tree/main/.ai/skills/automate-npm-release into .opencode/skills/automate-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-npm-release", 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
automate-npm-release- GitHub stars
- 161
- Token cost
- ~626 tokens
- SKILL.md length
- 228 words
- Files
- 5
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- None found
At a glance
Automate npm package publishing via GitHub Actions for single-package repos and independent monorepo packages, including bumpp version tags, GitHub release notes, trusted publishing, provenance, and…
- Modifying npm publish workflows
- SKILL.md covers Shared rules, Quick choice and Workflow examples
- Calls npm and pnpm; reaches registry.npmjs.org; needs NODE_AUTH_TOKEN
- Npm release pipelines
What it does
Automate npm Release is an agent skill from jd-solanki/slidev-theme-dracula. Automate npm package publishing via GitHub Actions for single-package repos and independent monorepo packages, including bumpp version tags, GitHub release notes, trusted publishing, provenance, and package-scoped release tags. Use when setting up or modifying npm publish workflows, npm release pipelines, version bumping, package-scoped monorepo releases, changelogithub release notes, trusted publishing, provenance badges, NPMTOKEN, or OIDC publishing.
Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `EXAMPLE_WORKFLOW.yml`, `MONOREPO.md` and `MONOREPO_WORKFLOW.yml`).
It sits in Development, covering Monorepo tooling, Changelog and release notes and OAuth and OpenID Connect. It works with npm, GitHub and GitHub Actions. The repository describes itself as: Dracula theme for slidev 🧛.
When your agent uses it
- Modifying npm publish workflows
- Npm release pipelines
- Version bumping
- Package-scoped monorepo releases
Example prompts
- “/automate-npm-release”
Requirements
- A credential in NPM_TOKEN
- A credential in NODE_AUTH_TOKEN
What it can do on your machine
Read from SKILL.md and the folder at commit 383e9b1. 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:
npmpnpm
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:
registry.npmjs.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
NODE_AUTH_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Automate npm Release loads about 626 tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 228 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 228 words (~626 tokens).
“Use this skill to set up npm release automation. First identify the repository shape, then load the matching reference:”
- name
- automate-npm-release
- disable-model-invocation
- true
Files
SKILL.md and 4 other files in .ai/skills/automate-npm-release of jd-solanki/slidev-theme-dracula.
- SKILL.md
- EXAMPLE_WORKFLOW.yml
- MONOREPO.md
- MONOREPO_WORKFLOW.yml
- SINGLE_PACKAGE.md
Open the folder on GitHubat commit 383e9b1
Compare with similar skills
Automate npm 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Automate npm Release this skilljd-solanki/slidev-theme-dracula | 161 | — | ~626 | Automated safety check: Pass | None | |
| Ccb GitHubSeemSeam/claude_codex_bridge | 3.6k | — | ~4.9k | Automated safety check: Pass | Custom licence | |
| Cline CLI Release Publishercline/cline | 70k | — | ~3.4k | Automated safety check: Warn | Apache-2.0 | |
| Linea Dependency MaintenanceConsensys-Incorporated/linea-attestation-registry | 177 | 1 repos | ~3.7k | Automated safety check: Warn | MIT | |
| ReleaseWebMCP-org/npm-packages | 104 | — | ~1.6k | Automated safety check: Notes | MIT | |
| npm Release Via GitHub Actionsjmfederico/pi-web | 871 | — | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Cline CLI Release Publisher
cline/cline
Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.
Linea Dependency Maintenance
Consensys-Incorporated/linea-attestation-registry
Safely plan and execute dependency maintenance for JavaScript/TypeScript (npm, pnpm) and GitHub Actions, including npm lockfiles, pnpm workspaces, catalogs, overrides, SHA-pinned action versions…
Release
WebMCP-org/npm-packages
Release the @mcp-b monorepo with Changesets and pnpm, using npm trusted publishing in GitHub Actions.
npm Release Via GitHub Actions
jmfederico/pi-web
A skill your agent uses whenever the user asks for a new npm version, npm release, package release, new release, version bump, publishing to npm, cutting a GitHub release, tagging a release, or…
npm Trusted Publishing
pr-pm/prpm
A skill your agent uses when setting up npm publishing with GitHub Actions - provides trusted publishing with OIDC, provenance attestations, and monorepo configuration
More from jd-solanki/slidev-theme-dracula
Clean Code
jd-solanki/slidev-theme-dracula
Write readable, maintainable code through disciplined naming, small functions, and clean error handling.
Comment Code
jd-solanki/slidev-theme-dracula
Write clear, useful in-code comments and documentation that capture what the code cannot say for itself.
Node CLI
jd-solanki/slidev-theme-dracula
Patterns and conventions for building Node.js CLI tools — src structure, entry point setup, Commander wiring, and update notifications.
Automate Commit Based Gh Release Changelog
jd-solanki/slidev-theme-dracula
Automate GitHub release creation and changelog generation from Conventional Commits using changelogithub — includes GitHub release mechanics, tag-based triggers, required permissions, and…
Code Organisation
jd-solanki/slidev-theme-dracula
Decide where code lives — the directory tree, module and package boundaries, and the layout inside a file.
Related
Works with
Categories
Questions about Automate npm Release
What does Automate npm Release do?
Automate npm package publishing via GitHub Actions for single-package repos and independent monorepo packages, including bumpp version tags, GitHub release notes, trusted publishing, provenance, and…. Automate npm Release is an agent skill from jd-solanki/slidev-theme-dracula. Automate npm package publishing via GitHub Actions for single-package repos and independent monorepo packages, including bumpp version tags, GitHub release notes, trusted publishing, provenance, and package-scoped release tags.
When should I use Automate npm Release?
Automate npm Release fits situations like: modifying npm publish workflows; npm release pipelines; version bumping; package-scoped monorepo releases.
How do I install Automate npm Release in Claude Code?
Run `npx skills add jd-solanki/slidev-theme-dracula --skill automate-npm-release -a claude-code`. Or copy the skill folder (.ai/skills/automate-npm-release in jd-solanki/slidev-theme-dracula) into .claude/skills/automate-npm-release in your project. Claude Code loads it when a task matches its description.
How do I install Automate npm Release in Codex?
Run `npx skills add jd-solanki/slidev-theme-dracula --skill automate-npm-release -a codex`. Or copy the skill folder (.ai/skills/automate-npm-release in jd-solanki/slidev-theme-dracula) into .agents/skills/automate-npm-release in your project. Codex loads it when a task matches its description.
Can I use Automate npm 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 jd-solanki/slidev-theme-dracula --skill automate-npm-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/automate-npm-release, .gemini/skills/automate-npm-release, .github/skills/automate-npm-release and .opencode/skills/automate-npm-release in your project.
What does Automate npm Release need to run?
Going by SKILL.md and its folder, Automate npm Release needs the command-line tools its instructions call (npm and pnpm) and credentials named NODE_AUTH_TOKEN. Our summary lists: A credential in NPM_TOKEN; A credential in NODE_AUTH_TOKEN.
Does Automate npm Release access the network?
SKILL.md names 1 domain. In commands or code: registry.npmjs.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Automate npm 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 Automate npm Release use?
No licence was found for Automate npm Release or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Automate npm Release use?
About 626 tokens (SKILL.md is roughly 2.5k 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 Automate npm Release?
Skills that share tags, products or a category with Automate npm Release: Ccb GitHub (SeemSeam/claude_codex_bridge, 3.6k stars), Cline CLI Release Publisher (cline/cline, 70k stars), Linea Dependency Maintenance (Consensys-Incorporated/linea-attestation-registry, 177 stars) and Release (WebMCP-org/npm-packages, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Automate npm Release?
jd-solanki (a GitHub user) maintains it in jd-solanki/slidev-theme-dracula, which has 161 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on July 6, 2026.
Source: jd-solanki/slidev-theme-dracula on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.