Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/testdino-hq/testdino-mcp --skill publishThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Scaffold and implement a new MCP tool end-to-end — endpoint, handler, registration, docs
Debug a malfunctioning MCP tool — trace the full request lifecycle to find the issue
Structured bug fix workflow — find issue in tracker, root-cause, fix, test, verify, document
Based on SOC occupation classification
Showing SKILL.md
| name | publish |
| description | Guided npm publish workflow — version bump, quality gate, build, publish, tag |
| argument-hint | [version: "patch", "minor", "major", or explicit like "1.1.0"] |
Prepare and publish a new version: $ARGUMENTS
This skill guides through the full release process. It does NOT auto-publish — it pauses for user confirmation at key points.
package.json$ARGUMENTS (default: patch)Current: X.Y.Z → New: A.B.CGet user confirmation before proceeding.
Verify the codebase is ready:
git status — working tree should be clean (no uncommitted changes)git branch — should be on main branchpackage.json, server.json, src/index.tsnpm run format:check — formatting is cleannpm run typecheck — no type errorsnpm run lint — no lint errorsnpm run test — all tests passnpm run build — build succeedsIf ANY check fails, stop and report. Do not continue with a broken build.
Update version in all 3 locations:
package.json → versionserver.json → version and packages[0].versionsrc/index.ts → server constructor versionnpm run build
The dist/ directory must reflect the new version.
Show git diff so the user can verify:
Get user confirmation before committing.
git add package.json server.json src/index.ts dist/
git commit -m "chore: Bump version to A.B.C"
git tag vA.B.C
Show the command but DO NOT run it automatically:
npm publish
git push origin main --tags
Tell the user to run these commands themselves.