From Plexus
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/plexus:bootstrap-plexus [--json] [--data-dir PATH][--json] [--data-dir PATH]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill before first use of Plexus, after plugin install/upgrade, or when
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
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
npx claudepluginhub jmagar/dendrite --plugin plexus