원클릭으로 Manus에서 모든 스킬 실행

pluxx-create-plugin

스타0

포크0

업데이트2026년 7월 12일 10:17

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

orchidautomation

orchidautomation/pluxx-plugin

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Create A Pluxx Plugin

Create the smallest deterministic source project before semantic refinement.

Workflow

Identify the source:
- already configured MCP: run pluxx discover-mcp, then use pluxx init --from-installed-mcp <host:name> --yes
- remote HTTP or SSE MCP: use pluxx init --from-mcp <url> --yes
- local stdio MCP: pass the complete executable command to --from-mcp
- host-native plugin: use pluxx migrate <path>
- no existing source: hand off pluxx init <name> to an interactive terminal; plain init rejects non-interactive execution
Read references/source-selection.md when transport, credentials, local runtimes, or autopilot choices are not obvious.
Use import-architect for unfamiliar MCP/runtime shape or migration-operator for host-native conversion when the host supports specialists.
Collect only the missing project choices: name, display name, source, target hosts, credential scheme, and whether to use the manual or one-shot path.
Prefer --dry-run when source detection, target selection, or generated file impact is uncertain.
Use workflow grouping and the core four unless the user asks for a narrower target set.
Run pluxx validate, pluxx doctor, pluxx lint, skills-ref validate for every source skill, and pluxx test after the source scaffold exists.
Route a valid but generic scaffold to pluxx-refine-plugin; route failed validation to pluxx-verify-plugin.

One-Shot Path

Use pluxx autopilot --from-mcp <source> --runner <runner> --mode standard --yes when the user explicitly prefers speed over inspecting each stage. Add --install --install-target <host> --trust only after the user requests a local install and the hook commands have been reviewed.

Safety

Never copy literal credential values into source files or output.
Prefer env variable names and platform-managed runtime configuration.
Treat generated dist/ as output; make fixes in the source project.

Output

Report the chosen path, generated source files, configured targets, credential shape without values, validation result, and the next refinement or proof step.

이 저장소의 다른 Skills

같은 저장소

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

Create A Pluxx Plugin

Create the smallest deterministic source project before semantic refinement.

Workflow

Identify the source:
- already configured MCP: run pluxx discover-mcp, then use pluxx init --from-installed-mcp <host:name> --yes
- remote HTTP or SSE MCP: use pluxx init --from-mcp <url> --yes
- local stdio MCP: pass the complete executable command to --from-mcp
- host-native plugin: use pluxx migrate <path>
- no existing source: hand off pluxx init <name> to an interactive terminal; plain init rejects non-interactive execution
Read references/source-selection.md when transport, credentials, local runtimes, or autopilot choices are not obvious.
Use import-architect for unfamiliar MCP/runtime shape or migration-operator for host-native conversion when the host supports specialists.
Collect only the missing project choices: name, display name, source, target hosts, credential scheme, and whether to use the manual or one-shot path.
Prefer --dry-run when source detection, target selection, or generated file impact is uncertain.
Use workflow grouping and the core four unless the user asks for a narrower target set.
Run pluxx validate, pluxx doctor, pluxx lint, skills-ref validate for every source skill, and pluxx test after the source scaffold exists.
Route a valid but generic scaffold to pluxx-refine-plugin; route failed validation to pluxx-verify-plugin.

One-Shot Path

Safety

Never copy literal credential values into source files or output.
Prefer env variable names and platform-managed runtime configuration.
Treat generated dist/ as output; make fixes in the source project.

Output

Report the chosen path, generated source files, configured targets, credential shape without values, validation result, and the next refinement or proof step.