Run any Skill in Manus with one click

bootstrap-plexus

Stars0

Forks0

UpdatedMay 24, 2026 at 06:50

Use when installing, setting up, repairing, or initializing the Plexus remote-device memory plugin; when the user asks where Plexus stores persistent REMOTE.md host profiles; or when seeded host profiles need to be created from bundled templates. Runs Plexus bootstrap to copy missing templates into plugin data without overwriting user-authored profiles.

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

jmagar

jmagar/.agents

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

SKILL.md

readonly

name	bootstrap-plexus
description	Use when installing, setting up, repairing, or initializing the Plexus remote-device memory plugin; when the user asks where Plexus stores persistent REMOTE.md host profiles; or when seeded host profiles need to be created from bundled templates. Runs Plexus bootstrap to copy missing templates into plugin data without overwriting user-authored profiles.
argument-hint	[--json] [--data-dir PATH]

Bootstrap Plexus

Use this skill before first use of Plexus, after plugin install/upgrade, or when the user asks to repair missing host profiles.

Dynamic Bootstrap

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

Persistent Data Contract

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.

After Bootstrap

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

More from this repository

same repository

android-app-testing

jmagar/.agents

Use when the user wants to live-test an Android APK end-to-end on an emulator/device and get a works/doesn't-work + UI/UX report — driving the real app, not writing test code. Triggers: "test my Android app", "QA this APK", "run the app on the emulator and tell me what breaks", "click through every screen", "review the app's UX", "does my APK work", "test the built APK". Installs/launches the APK, enumerates screens from the accessibility tree, exercises each feature via adb (tap/type/swipe/launch), watches logcat for crashes/ANRs, captures screenshots + UI dumps, and emits a structured report. Primary path is direct local adb; optional richer path via claude-in-mobile. Sibling of web-app-testing and desktop-app-testing (shared report format). Does NOT fire for: building/coding an Android app (use claude-android-ninja / jetpack-compose-expert), iOS, or unit tests.

2026-05-300

desktop-app-testing

jmagar/.agents

Use when the user wants to live-test a built Windows desktop application (.exe) end-to-end inside the agent-os Windows 11 VM and get a works/doesn't-work + UI/UX report — launching the real binary and driving it, not writing test code. Triggers: "test my Windows app", "QA this .exe", "run my desktop build on agent-os and tell me what breaks", "click through the app", "review the desktop app's UX", "does my exe work", "test the built binary in the Windows VM". Gets the .exe into the VM, launches it, enumerates controls from the UI Automation tree, drives every feature (click/type by element), watches for crashes/hangs/error dialogs, captures screenshots + control-tree dumps, and emits a structured report. Drives the agent-os VM via the Windows-MCP gateway. Sibling of web-app-testing and android-app-testing (shared report format). Does NOT fire for: building/coding a desktop app, the user's personal Windows on steamy (use nircmd), or general agent-os VM driving (use agent-os).

2026-05-300

web-app-testing

jmagar/.agents

Use when the user wants to live-test a WEB app/site end-to-end in a real browser and get a works/doesn't-work + UI/UX report — not just write Playwright code. Triggers: "test my web app", "QA this site", "run E2E on the web app", "click through every feature and tell me what breaks", "review the UX of this web app", "does my web app work", "test the deployed site". Drives a real Chrome via Playwright over CDP (default http://127.0.0.1:9222), enumerates features from the DOM/ARIA tree, exercises each, captures screenshots + console/page/network errors, and emits a structured report. Sibling of android-app-testing and desktop-app-testing (shared report format). Does NOT fire for: writing a one-off Playwright script (use webwright), pure web design/build with no testing, or backend/API-only testing.

2026-05-300

broadcastr

jmagar/.agents

Read or interact with the broadcastr activity feed across concurrent Claude sessions. Use when the user says "what are other agents doing", "show recent activity", "mute plan-exec notifications", "what's on the bus", "broadcastr status", "tail broadcastr", "emit a manual broadcastr event", or asks why a notification appeared. Also use to disable broadcastr in the current session (BROADCASTR_DISABLED=1) or check the global feed. Does NOT fire on generic "show me activity" or "what's happening" unless broadcastr is explicitly named.

2026-05-270

work-it

jmagar/.agents

Use when the user asks to "work it", execute a superpowers executing-plans document in a worktree, create a PR as soon as the implemented plan is green, or run a complete review-and-fix loop over all touched files.

2026-05-260

yt-dlp

jmagar/.agents

Use when the user asks to download, archive, search, inspect, or organize media with yt-dlp, MeTube, YouTube, playlists, channels, supported video sites, audio extraction, metadata, thumbnails, subtitles, Plex yt-dlp libraries, or NAS media downloads.

2026-05-260

name	bootstrap-plexus
description	Use when installing, setting up, repairing, or initializing the Plexus remote-device memory plugin; when the user asks where Plexus stores persistent REMOTE.md host profiles; or when seeded host profiles need to be created from bundled templates. Runs Plexus bootstrap to copy missing templates into plugin data without overwriting user-authored profiles.
argument-hint	[--json] [--data-dir PATH]

Bootstrap Plexus

Use this skill before first use of Plexus, after plugin install/upgrade, or when the user asks to repair missing host profiles.

Dynamic Bootstrap

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

Persistent Data Contract

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.

After Bootstrap

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