npm-workflow-release
Release agent-harness packages to npm and verify publication. Use when the user asks to cut a release, push a missing release tag, or troubleshoot why a version was not published.
Best use case
npm-workflow-release is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Release agent-harness packages to npm and verify publication. Use when the user asks to cut a release, push a missing release tag, or troubleshoot why a version was not published.
Teams using npm-workflow-release should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/npm-workflow-release/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How npm-workflow-release Compares
| Feature / Agent | npm-workflow-release | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Release agent-harness packages to npm and verify publication. Use when the user asks to cut a release, push a missing release tag, or troubleshoot why a version was not published.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# npm-workflow-release Run the release workflow for this repository end-to-end. Use `$ARGUMENTS` as the target version when provided (for example: `1.6.0` or `v1.6.0`). ## Steps 1. Resolve the target version. - If `$ARGUMENTS` is provided, normalize it to `X.Y.Z` and `vX.Y.Z`. - If not provided, infer the intended version from context and confirm package files match. 2. Validate lockstep package versions. - Check `packages/manifest-schema/package.json` and `packages/toolkit/package.json`. - Ensure both `version` values are identical and equal to the target version. 3. Confirm release workflow prerequisites. - Check `.github/workflows/publish-npm.yml` triggers on tag push (`v*`). - Run `GITHUB_REF_NAME=vX.Y.Z pnpm run release:guard` before publishing. 4. Ensure the release tag exists remotely. - Check local and remote tags for `vX.Y.Z`. - If missing on remote, push it: `git push origin vX.Y.Z`. 5. Monitor the publish run in GitHub Actions. - Use `gh run list --workflow publish-npm.yml`. - Watch the matching run with `gh run watch <run-id> --exit-status`. 6. Verify npm publication for both packages. - `npm view @madebywild/agent-harness-manifest dist-tags --json` - `npm view @madebywild/agent-harness-framework dist-tags --json` - Confirm `latest` (or requested tag) points to `X.Y.Z`. 7. Report outcome with concrete evidence. - Include tag push result, workflow run id/status, and npm verification output summary. ## Troubleshooting - If no workflow run appears, the tag was likely not pushed to remote. - If prepublish fails, fix version mismatch or tag mismatch first. - If publish fails with auth errors, confirm `NPM_TOKEN` in GitHub Actions secrets. - If verify-published fails due lag, retry after npm propagation delay.
Related Skills
harness-subagent
Create and manage subagent entities in the agent-harness workspace. Invoke this skill when a user wants to define, scaffold, apply, or remove a subagent across Claude Code, OpenAI Codex, or GitHub Copilot.
harness-skill
Create and manage skill entities in the agent-harness workspace. Use when the user wants to add a new skill, understand how skills work across providers, or generate provider skill artifacts from a canonical source.
harness-settings
Configure provider-specific settings (permissions, model, features) for Claude Code, OpenAI Codex CLI, and GitHub Copilot using the harness settings entity.
harness-prompt
Create and manage the system prompt entity in agent-harness, generating CLAUDE.md, AGENTS.md, and copilot-instructions.md from a single canonical source.
harness-mcp
Create and manage MCP server config entities in the agent-harness workspace.
harness-hook
Create and manage lifecycle hook entities in the agent-harness workspace. Covers canonical event authoring, provider projection (Claude Code, GitHub Copilot, OpenAI Codex CLI, Cursor), mode behavior, handler types, the full event/provider support matrix, copy-paste recipes, and common diagnostics.
securing-github-actions-workflows
This skill covers hardening GitHub Actions workflows against supply chain attacks, credential theft, and privilege escalation. It addresses pinning actions to SHA digests, minimizing GITHUB_TOKEN permissions, protecting secrets from exfiltration, preventing script injection in workflow expressions, and implementing required reviewers for workflow changes.
secure-workflow-guide
Guide you through Trail of Bits' 5-step secure development workflow. Runs Slither scans, checks special features (upgradeability/ERC conformance/token integration), generates visual security diagrams, helps document security properties for fuzzing/verification, and reviews manual security areas. (project, gitignored)
implementing-patch-management-workflow
Patch management is the systematic process of identifying, testing, deploying, and verifying software updates to remediate vulnerabilities across an organization's IT infrastructure. An effective patc
designing-workflow-skills
Guides the design and structuring of workflow-based Claude Code skills with multi-step phases, decision trees, subagent delegation, and progressive disclosure. Use when creating skills that involve sequential pipelines, routing patterns, safety gates, task tracking, phased execution, or any multi-step workflow. Also applies when reviewing or refactoring existing workflow skills for quality.
building-vulnerability-scanning-workflow
Builds a structured vulnerability scanning workflow using tools like Nessus, Qualys, and OpenVAS to discover, prioritize, and track remediation of security vulnerabilities across infrastructure. Use when SOC teams need to establish recurring vulnerability assessment processes, integrate scan results with SIEM alerting, and build remediation tracking dashboards.
building-phishing-reporting-button-workflow
Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.