Run any Skill in Manus with one click

pluxx-publish-plugin

Stars0

Forks0

UpdatedJuly 12, 2026 at 10:17

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.

Installation

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.

Run Skill in Manus

Source

orchidautomation

orchidautomation/pluxx-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

5 files

SKILL.md

readonly

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.

Publish A Pluxx Plugin

Turn verified source into honest, reproducible release artifacts.

Workflow

Confirm the requested path: dry-run, GitHub Release, npm, or both.
Read references/release-checklist.md before any real publish or when public proof claims are part of the release.
Use release-operator for the release path or proof-publisher for public proof assets when the host supports specialists.
Verify the project with pluxx validate, pluxx doctor, pluxx lint, skills-ref validate for every source skill, and pluxx test.
Confirm the working tree, version, tag, repository, generated targets, and strongest completed proof layer.
Preview first:
- pluxx publish --dry-run
- add --github-release, --npm, and --version <x.y.z> to match the intended channels; --tag <name> selects only the npm dist-tag
- use --allow-dirty only for an intentional local or CI plan, never to hide unknown changes
Package proof assets only from completed evidence: install links, screenshots, behavior notes, reload instructions, and host caveats.
Upload only after explicit approval. Run the exact reviewed publish command.
Report bundles, installers, checksums, manifest, tags, URLs, and any remaining distribution caveats.

Release Truth

Raw main installer links work after the installer files are pushed.
releases/latest/download/... works only after a tagged GitHub release exists.
A release must not claim behavioral proof when only source or build checks ran.
Expected host translations belong in release notes when they affect user expectations.
Publishing is an external side effect; never infer approval from a request to review or prepare artifacts.

Output

Return the release mode, version, verification evidence, exact publish action, generated artifacts, public install paths, and blockers or follow-up.

More from this repository

same repository

pluxx-create-plugin

orchidautomation/pluxx-plugin

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.

2026-07-120

pluxx-guide

orchidautomation/pluxx-plugin

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.

2026-07-120

pluxx-maintain-plugin

orchidautomation/pluxx-plugin

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.

2026-07-120

pluxx-refine-plugin

orchidautomation/pluxx-plugin

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.

2026-07-120

pluxx-translate-hosts

orchidautomation/pluxx-plugin

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.

2026-07-120

pluxx-verify-plugin

orchidautomation/pluxx-plugin

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.

2026-07-120

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.

Publish A Pluxx Plugin

Turn verified source into honest, reproducible release artifacts.

Workflow

Confirm the requested path: dry-run, GitHub Release, npm, or both.
Read references/release-checklist.md before any real publish or when public proof claims are part of the release.
Use release-operator for the release path or proof-publisher for public proof assets when the host supports specialists.
Verify the project with pluxx validate, pluxx doctor, pluxx lint, skills-ref validate for every source skill, and pluxx test.
Confirm the working tree, version, tag, repository, generated targets, and strongest completed proof layer.
Preview first:
- pluxx publish --dry-run
- add --github-release, --npm, and --version <x.y.z> to match the intended channels; --tag <name> selects only the npm dist-tag
- use --allow-dirty only for an intentional local or CI plan, never to hide unknown changes
Package proof assets only from completed evidence: install links, screenshots, behavior notes, reload instructions, and host caveats.
Upload only after explicit approval. Run the exact reviewed publish command.
Report bundles, installers, checksums, manifest, tags, URLs, and any remaining distribution caveats.

Release Truth

Raw main installer links work after the installer files are pushed.
releases/latest/download/... works only after a tagged GitHub release exists.
A release must not claim behavioral proof when only source or build checks ran.
Expected host translations belong in release notes when they affect user expectations.
Publishing is an external side effect; never infer approval from a request to review or prepare artifacts.

Output

Return the release mode, version, verification evidence, exact publish action, generated artifacts, public install paths, and blockers or follow-up.