一键在 Manus 中运行任何 Skill

pluxx-maintain-plugin

星标0

分支0

更新时间2026年7月12日 10:17

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

orchidautomation

orchidautomation/pluxx-plugin

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Maintain A Pluxx Plugin

Refresh generated source without losing user-owned work.

Workflow

Confirm that .pluxx/mcp.json exists and the project is MCP-derived.
Inspect the working tree. Do not sync across unrelated uncommitted changes without isolating or preserving them.
Preview first:
- pluxx sync --dry-run --json
- use --from-mcp <source> only when the canonical source changed intentionally
Read references/sync-safety.md before applying sync, or whenever the preview contains removed, preserved, renamed, or warning entries.
Review added, updated, removed, preserved, renamed, and warning entries before applying.
Run pluxx sync after the preview is understood.
Inspect mixed-ownership Markdown boundaries and any custom notes attached to removed generated surfaces.
Run pluxx validate, pluxx doctor, pluxx lint, pluxx eval, and pluxx test; run skills-ref validate for every source skill.
Route changed product meaning, tool grouping, or setup behavior to pluxx-refine-plugin.

Drift Rules

Never delete preserved custom content silently.
Call out removed MCP tools that strand a workflow or custom note.
Treat persisted taxonomy and invalidated agent packs as explicit review work, not incidental generated noise.
Keep source fixes in the root project and rebuild dist/ through Pluxx.
Treat a changed local stdio command or payload path as a runtime change that needs install verification.

Output

Report the source used, preview summary, applied changes, preserved content, warnings, validation result, and any refinement or install-proof follow-up.

同仓库更多 Skills

同仓库

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-publish-plugin

orchidautomation/pluxx-plugin

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.

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-maintain-plugin
description	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.

Maintain A Pluxx Plugin

Refresh generated source without losing user-owned work.

Workflow

Confirm that .pluxx/mcp.json exists and the project is MCP-derived.
Inspect the working tree. Do not sync across unrelated uncommitted changes without isolating or preserving them.
Preview first:
- pluxx sync --dry-run --json
- use --from-mcp <source> only when the canonical source changed intentionally
Read references/sync-safety.md before applying sync, or whenever the preview contains removed, preserved, renamed, or warning entries.
Review added, updated, removed, preserved, renamed, and warning entries before applying.
Run pluxx sync after the preview is understood.
Inspect mixed-ownership Markdown boundaries and any custom notes attached to removed generated surfaces.
Run pluxx validate, pluxx doctor, pluxx lint, pluxx eval, and pluxx test; run skills-ref validate for every source skill.
Route changed product meaning, tool grouping, or setup behavior to pluxx-refine-plugin.

Drift Rules

Never delete preserved custom content silently.
Call out removed MCP tools that strand a workflow or custom note.
Treat persisted taxonomy and invalidated agent packs as explicit review work, not incidental generated noise.
Keep source fixes in the root project and rebuild dist/ through Pluxx.
Treat a changed local stdio command or payload path as a runtime change that needs install verification.

Output

Report the source used, preview summary, applied changes, preserved content, warnings, validation result, and any refinement or install-proof follow-up.