菜单
Use this skill when a user wants to package, preview, or publish a Pluxx release, including GitHub Releases, npm, installers, checksums, screenshots, proof notes, or install links. Require verification and explicit approval before upload.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when a user wants to create a Pluxx project from a raw or installed MCP, local stdio command, blank project, or existing Claude Code, Cursor, Codex, or OpenCode plugin, including the one-shot autopilot path.
Use this skill when a user asks how to install, upgrade, choose a command for, or orient themselves in the Pluxx CLI, including broad “what next?” questions and ambiguous runtime/setup failures. Route plugin-project failures to verification.
Use this skill when an existing MCP-derived Pluxx project must be refreshed after its MCP, docs, runtime, or scaffold inputs change. Preview and run sync, preserve custom sections, explain drift, and route semantic changes to refinement.
Use this skill when a valid Pluxx scaffold is generic, tool-shaped, fragmented, or unclear. Apply product context, improve workflow taxonomy, rewrite shared instructions, or run a findings-first scaffold review.
Use this skill when a user asks what a Pluxx source preserves, translates, degrades, or drops across Claude Code, Cursor, Codex, and OpenCode. Audit the relevant compiler buckets and recommend source-shape fixes.
Use this skill when a user wants to validate, lint, evaluate, build, test, install, verify, troubleshoot, or behaviorally prove a Pluxx plugin. Separate source, build, installed-state, and real workflow evidence.
| name | pluxx-publish-plugin |
| description | Use this skill when a user wants to package, preview, or publish a Pluxx release, including GitHub Releases, npm, installers, checksums, screenshots, proof notes, or install links. Require verification and explicit approval before upload. |
Turn verified source into honest, reproducible release artifacts.
release-operator for the release path or proof-publisher for public proof assets when the host supports specialists.pluxx validate, pluxx doctor, pluxx lint, skills-ref validate for every source skill, and pluxx test.pluxx publish --dry-run--github-release, --npm, and --version <x.y.z> to match the intended channels; --tag <name> selects only the npm dist-tag--allow-dirty only for an intentional local or CI plan, never to hide unknown changesmain installer links work after the installer files are pushed.releases/latest/download/... works only after a tagged GitHub release exists.Return the release mode, version, verification evidence, exact publish action, generated artifacts, public install paths, and blockers or follow-up.