plugins/lisa-cursor/skills/plugin-sync-explain/SKILL.md
Read-only diagnostic for Lisa plugin source/generated drift. Compares plugins/src against generated plugins/lisa* status, reports source-not-built, generated-only, and marketplace registration drift, and preserves the working tree.
npx skillsauth add codyswanngt/lisa plugin-sync-explainInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
/lisa:plugin-sync-explain explains why the plugin sync gate would need attention without mutating the working tree.
Inspect the current Lisa repository, or an optional path passed as $ARGUMENTS, using scripts/plugin-sync-explain.mjs.
The diagnostic is read-only:
bun run build:plugins.bun run check:plugins..claude-plugin/marketplace.json.Report a concise terminal-first summary with stable classifications:
SOURCE_NOT_BUILT: files under plugins/src/** changed without their generated plugins/lisa* counterpart.GENERATED_ONLY: files under plugins/lisa* changed without their plugins/src/** source counterpart.MARKETPLACE_REGISTRATION_DRIFT: a built plugin directory is missing from .claude-plugin/marketplace.json, or a marketplace source points at a missing built directory.OUT_OF_SYNC: source and generated counterparts both changed and need human review.IN_SYNC: no plugin source/generated or marketplace registration drift was detected.For every finding, include the evidence path and the smallest source-first next action. Prefer bun run build:plugins only after source edits are in the right place, and preserve bun run check:plugins as the final reproducibility gate.
$ARGUMENTS or the current directory.git status --porcelain before the diagnostic.node plugins/lisa/scripts/plugin-sync-explain.mjs "$REPO_PATH"
If running from the source tree before generated artifacts are rebuilt, use:
node plugins/src/base/scripts/plugin-sync-explain.mjs "$REPO_PATH"
git status --porcelain after the diagnostic and confirm it is unchanged.scripts/check-plugins-sync.sh; it explains the gate but does not replace it.plugins/src/** as the source of truth and plugins/lisa* as generated artifacts.development
Prepare a machine — a fresh laptop or a throwaway container — to run coding agents, before any repository exists. Detects which of Lisa's supported agents (Claude Code, Codex, Cursor, OpenCode, Antigravity, Copilot) are already installed, asks which credential manager the machine uses (Bitwarden, 1Password, Doppler, Vault, AWS, or none), and installs only what is missing, each by its vendor's own preferred method. Idempotent, headless by default, and emits a Dockerfile for a spin-up/spin-down environment. Run it on a new machine, in a container, or before cloning anything.
tools
Provision and verify a remote execution environment for a host project — Codex Cloud today, other remote surfaces as they are added. Generates a repository-owned setup script that installs the declared toolchain, materializes secrets through lisa-secrets-access, and runs the project's own hook. Provisions by API where one exists, by driving the vendor console where one does not, and by emitting exact config otherwise — then proves the result with the same read-back regardless of which tier did the work. Use before dispatching any work with executionEnv.
tools
Bring a developer's machine in line with the toolchain the project declares. Reports every tool in remoteEnv.tools that is missing, outdated, or unpinned for this platform, and installs the missing ones into ~/.local/bin from the same pinned, checksummed entries the remote surfaces use — but only when asked. Same manifest, same pins, same installers as lisa-setup-remote-env; what differs is consent and that the pin is a floor rather than an equality. Run it on a fresh checkout, after a manifest change, or when a tool fails at the moment of use.
tools
Route one unit of work to a remote execution surface. Reads the executionEnv parameter (local by default, codex-cloud or claude-web today), verifies the environment is provisioned and bound to this repository, submits a thin skill invocation, records the task identifier to .lisa/remote-dispatch.json, and exits without polling. Routing only — the remote runs the identical skill from the identical repository. Composable and inline: other skills invoke it via the Skill tool rather than users calling it directly.