Skill0 repo starsupdated yesterday

workflows

The publish-skill command validates and publishes MindForge skills to npm registries after running pre-publication checks including version verification, changelog confirmation, and package content preview. Use this command when ready to release a skill to npm, with optional dry-run and custom registry support for testing publication workflows before committing changes.

View source Repository: MindForge

Install in Claude Code

Copy

git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/workflows && cp -r /tmp/workflows/.agent/workflows/mindforge:publish- ~/.claude/skills/workflows

Then start a new Claude Code session; the skill loads automatically.

Definition

mindforge:publish-skill.md

# MindForge — Publish Skill Command
# Usage: /mindforge:publish-skill [skill-dir] [--registry URL] [--dry-run]

Publish a skill to the npm registry (or private registry).

Pre-publication checklist:
1. Run full skill validation (Level 1 + 2 + 3 from skill-validator.md)
   Fail if Level 1 or 2 fails. Warn if Level 3 fails.
2. Verify package.json has `mindforge` field with all required sub-fields
3. Verify CHANGELOG.md has an entry for the current version
4. Check if version already published: `npm info [package-name]@[version]`
   If already published: error "Version already exists. Bump the version."
5. Run `npm pack --dry-run` to preview what will be published
6. Confirm with user: "These files will be published: [list]. Proceed? (yes/no)"
7. If --dry-run: stop here, show preview only
8. Publish: `npm publish --access public`
9. Verify: `npm info [package-name]@[version]` — confirm publication succeeded
10. Write AUDIT: `{ "event": "skill_published", "package": "...", "version": "..." }`
11. Report: "✅ [package-name]@[version] published to npm registry"