skills/mage-remote-run/SKILL.md
Guidance for using the Mage Remote Run CLI to manage Adobe Commerce, Magento Open Source, and Mage-OS instances remotely. Use when a user needs to: inspect or manage a remote Adobe Commerce, Magento Open Source, or Mage-OS instance; get help with mage-remote-run commands, flags, filters, or workflow design; configure connections, authentication, MCP server mode, plugins, or the interactive console; suggest automation-friendly command examples for CI/CD, scripts, or agent integrations.
npx skillsauth add muench-dev/agent-skills mage-remote-runInstall 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.
Mage Remote Run is a CLI toolkit for operating Adobe Commerce, Magento Open Source, and Mage-OS environments remotely. It supports SaaS, Cloud/PaaS, and on-premise deployments with commands covering stores, customers, orders, products, inventory, shipments, webhooks, imports, and more. Output can be rendered as text, JSON, or XML.
mage-remote-run command examples over abstract descriptions.--format json when machine-readable output may be useful.Load these as needed:
tools
Build, explain, and maintain `mage-remote-run` plugins and configuration-based extensions. Use when an agent needs to create or review plugin packages, register custom commands, hook into plugin lifecycle events, inject or persist CLI configuration, ship static `mage-remote-run.json` settings, or define virtual commands for Magento or Adobe Commerce APIs.
development
The linter checks the docker setup and lints all files
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------