x-setuplisted

Check and explain an elon-musk plugin install across Codex cache, marketplace metadata, direct skill-home symlinks, prompt visibility, and validation commands. Use when the user says check install, is it loaded, setup doctor, why is the skill missing, or how to fix local harness setup. Do not use for method reviews of product strategy, or to delete plugins/edit global config without an explicit ask.
thepraggyverse/elon-musk · ★ 0 · AI & Automation · score 70

Install: claude install-skill thepraggyverse/elon-musk

# X Setup (shared-meta shim) ## Pack Context - Pack config: `owned/shared-meta-skills/pack-configs/elon-musk.yaml` - Shared template: `owned/shared-meta-skills/skills/shared-setup/SKILL.md` - Canonical pack: `owned/elon-musk` - Pack-local reference: `owned/elon-musk/docs/INSTALL.md` - Pack-local reference: `owned/elon-musk/docs/HARNESS_MATRIX.md` - Direct-install fallback: `references/README.md` - Direct-install fallback: `references/INSTALL.md` - Direct-install fallback: `references/HARNESS_MATRIX.md` ## Procedure 1. Load `setup` and `shim_contracts.x-setup` from the pack config. 2. Load only the pack-local references named by the shim and config. 3. Follow `shared-setup` for the invariant workflow and output contract. 4. Apply the configured pack-specific behavior, fields, and boundary without weakening the shared guardrails. 5. Run python3 scripts/check_install.py --plugin when available and add --prompt-input only when prompt visibility is in scope. ## Pack-specific behavior preserved - Distinguish installed state across marketplace, plugin link, cache, and direct skill homes. - Distinguish prompt visibility from installed-on-disk state. - For direct skill links, require an explicit profile: agents, codex, or claude. - Treat OpenClaw and OpenClaw ACPX profiles as retired on Praggy's system; do not recreate them. - Return one targeted reinstall, cache refresh, restart, skill-root reduction, or direct invocation command. ## Output Contract - Installed state - Prompt