菜单
This skill should be used when the user wants to install, set up, repair, or initialize the Plexus remote-device memory plugin; when they ask where Plexus stores persistent REMOTE.md host profiles; or when host profiles are missing and need to be seeded from bundled defaults.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when creating, editing, validating, testing, running, explaining, or removing Labby Code Mode snippets; when a user wants a reusable workflow made from gateway MCP tools; or when building schema-backed snippets from upstream tool ids, JSON schemas, params, inputs, defaults, artifacts, and MCP/CLI snippet actions.
Use when creating, editing, validating, testing, running, explaining, or removing Labby Code Mode snippets; when a user wants a reusable workflow made from gateway MCP tools; or when building schema-backed snippets from upstream tool ids, JSON schemas, params, inputs, defaults, artifacts, and MCP/CLI snippet actions.
This skill should be used when the user wants to automate an iOS Simulator, drive an Android device or emulator via MCP tools, test on multiple devices simultaneously, run a visual regression baseline on mobile, audit accessibility on a real device, release an app to the Play Store, or use the claude-in-mobile CLI or MCP server. Does not apply for structured end-to-end test reports (use android-app-testing or desktop-app-testing for those).
Interpret and use `mcpjam` probe, doctor, OAuth, apps conformance, tools, resources, and prompts output conservatively against MCP 2025-11-25. Use when interacting with MCP servers, executing tools, triaging findings, performing security reviews, deciding whether a CLI finding is real or overstated, or turning inspection output into an engineer-facing report with severity and confidence.
Audit the current Git checkout, open worktrees, local branches, stale or merged cleanup candidates, merge readiness, conflicts, PR/CI/test state, blockers, and safest merge order. Use when the user asks for repo status, branch/worktree cleanup candidates, stale branch review, conflict investigation, merge readiness, or what must be done before open branches can merge.
This skill should be used when the user mentions labby, the labby CLI, the Lab gateway, or any Lab operator surface. Triggers include: "run labby doctor", "check labby health", "start the labby MCP server", "configure ~/.lab/.env", "search upstream MCP tools with Code Mode", "use labby gateway to import servers", "manage the Labby marketplace", "reload the gateway", or any request to run labby CLI commands, inspect gateway upstreams, or dispatch an action against a Lab service.
| name | bootstrap-plexus |
| description | This skill should be used when the user wants to install, set up, repair, or initialize the Plexus remote-device memory plugin; when they ask where Plexus stores persistent REMOTE.md host profiles; or when host profiles are missing and need to be seeded from bundled defaults. |
| argument-hint | [--json] [--data-dir PATH] |
Use this skill before first use of Plexus, after plugin install/upgrade, or when the user asks to repair missing host profiles.
This initializes missing persistent profiles from bundled templates. It never
overwrites existing REMOTE.md files.
!python3 "${CLAUDE_PLUGIN_ROOT:-plugins/plexus}/scripts/remote-context.py" --init $ARGUMENTS
Plexus must not store mutable host memory in the plugin source tree. Bundled
files under ${CLAUDE_PLUGIN_ROOT:-plugins/plexus}/templates/remotes/ are
defaults only.
Persistent host profiles live at:
${CLAUDE_PLUGIN_DATA}/remotes/<host>/REMOTE.md
During local development outside an installed plugin, the fallback is:
~/.plexus/remotes/<host>/REMOTE.md
The user can override this with PLEXUS_DATA_DIR or --data-dir.
Report the data directory and any profiles seeded. If a profile already exists, leave it untouched and tell the user it was preserved.
To inspect a seeded profile:
python3 "${CLAUDE_PLUGIN_ROOT:-plugins/plexus}/scripts/remote-context.py" <host> --no-probe