REPO PACKAGE
medusajs medusa-agent-skills
COMMUNITY17skills
3ready to use
LABSCO SUMMARY
Eight skills are the medusa-cloud cluster: using-medusa-cloud is the umbrella entry point, and one skill exists per area of the mcloud CLI — auth, deployments, environments, logs, organizations, projects, and variables. learning-medusa is a separate, single interactive-tutorial skill that walks a newcomer through building a "brands" feature step by step. The remaining eight — building-admin-dashboard-customizations, building-storefronts, building-with-medusa, creating-agents-in-medusa, db-generate, db-migrate, new-user, and storefront-best-practices — are the core open-source surface: backend modules and workflows, admin-dashboard UI, storefront integration, scaffolding a migration or an admin user, and building an internal (merchant-facing, not customer-facing) agent inside a Medusa project.
This is for a developer building an actual Medusa store, admin dashboard, or storefront — the "REQUIRED for all X work in ALL modes" wording on several skills means they're meant to load on nearly every task in their area, not just narrow ones. The medusa-cloud cluster is only relevant once you actually have a Medusa Cloud account and the mcloud CLI logged in; without one, eight of the seventeen skills have nothing to do.
READ THE FULL ANALYSIS
Two skills claim the same territory. building-storefronts and storefront-best-practices both describe themselves as required for essentially all storefront work — cart, checkout, product pages, navigation — and neither README table nor either skill's own description says which one an agent should prefer when both match.
Installation depends on which agent you use. Claude Code gets the easy path: /plugin marketplace add medusajs/medusa-agent-skills, then /plugin install <plugin>@medusa. Other agents use yarn skills add medusajs/medusa-agent-skills, which copies the skill files only — it cannot bring along the MCP server that some of these plugins also ship, so a Cursor or similar user has to add that server's config by hand.
Checked 19 September 2026 against medusajs/medusa-agent-skills's own README and skill descriptions.
ALSO IN THIS PACKAGE
PLUGINS
4 itemsPLUGIN
medusa-dev
Comprehensive skills for building Medusa applications: backend (modules, workflows, API routes), admin UI (widgets, forms, tables), and storefronts (SDK integration, React Query).
PLUGIN
learn-medusa
Interactive guided tutorial for learning Medusa development. Teaches you to build custom features step-by-step with a brands example.
PLUGIN
ecommerce-storefront
Comprehensive skills for building ecommerce storefronts with best practices for UI/UX, SEO, and mobile responsiveness
PLUGIN
medusa-cloud
Skills for managing Medusa Cloud resources through the Cloud CLI (mcloud). Covers setup, deployments, debugging, local build reproduction, environment variable management, environment management, organizations, projects, logs, and authentication.
PROMPT TEMPLATES
1 itemPROMPT TEMPLATE
sync medusa docs changes
MCP SERVERS
2 itemsMCP SERVER
MedusaDocs
http · https://docs.medusajs.com/mcpMCP SERVER
MedusaDocs
http · https://docs.medusajs.com/mcpWHAT'S INSIDE
17 showing · 17 totalReady to use
Nothing else to set up — install it and go.
17 of 17
SETUP
Showing all 17 skills
building-admin-dashboard-customizations
An online store built on Medusa comes with a back office where staff handle products and orders, and this is how you add your own screens and panels to it so they look and behave like the ones already there.
building-storefronts
Most of what breaks on the shopper-facing side of a Medusa store is the same handful of mistakes in how the page asks the server for products, carts and orders — here they are, with what to do instead.
building-with-medusa
Anything new you add to the server side of a Medusa store has to be built in a fixed order — where the data lives, then the rules that change it, then the address the rest of the shop calls — and this lays out that order.
creating-agents-in-medusa
Staff running a Medusa shop can be given a chat box inside the back office and ask for what they need in plain words instead of clicking through screens — this is how that assistant gets built, and kept to staff only.
db-generate
Changing what information a Medusa store keeps means the database has to change to match; this writes out that change as a file, ready to be applied.
db-migrate
Applies the database changes that have been written but not yet run, so a Medusa project's database matches the code.
learning-medusa
Three guided lessons in which the assistant teaches Medusa the way an instructor would: explaining each piece, checking you followed it, and not moving on until your code actually runs.
mcloud-auth
Signs you in to Medusa Cloud from the command line and picks which organization, project and environment you are working on, including on machines with no browser to log in through.
mcloud-deployments
Every push of a Medusa Cloud store to the live site leaves a record — this pulls up those records and the build output behind them, so you can see whether the last one worked and what went wrong if it didn't.
mcloud-environments
A Medusa Cloud project can run several separate copies of the same store — the live one, a staging one, one off a test branch — and this is how you create, inspect, delete and restart them.
mcloud-logs
Pulls up the running record of what a live Medusa Cloud store is doing — every request and error it writes down — narrowed to a time window, a search word, or one particular release.
mcloud-organizations
An organization on Medusa Cloud is the company account that owns your projects and pays the bill; these commands find the ones you belong to and read what is inside them.
mcloud-projects
Finds the Medusa Cloud projects your account can see and what each one is wired up to — which code repository, which running copies of the store — and deletes one for good when it is no longer wanted.
mcloud-variables
The settings and secret keys a live Medusa Cloud store runs on can be read, added, changed or removed here, with secret values kept hidden unless you ask for them.
new-user
Anyone who needs to get into a Medusa store's back office needs a login of their own, and this creates one from an email address and password you pick.
storefront-best-practices
A shop page that quietly loses sales is usually breaking one of a well-known set of rules — about layout, phones, search listings and shoppers who use assistive technology — and this is that set of rules.
using-medusa-cloud
Runs a Medusa Cloud online store from the command line: pushing a new version live, reading the logs when a build fails, and changing settings without spilling the secret ones onto the screen.
No skill in this package matches that.
HOW TO GET IT
WHOLE PACKAGEInstall the whole package (17 skills)
npx skills add medusajs/medusa-agent-skillsSINGLE SKILLOr install a single skill
npx skills add medusajs/medusa-agent-skills --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.
PLUGIN MARKETPLACEAdd the marketplace, then install the plugins you want
/plugin marketplace add medusajs/medusa-agent-skills/plugin install medusa-dev@medusa/plugin install learn-medusa@medusa/plugin install ecommerce-storefront@medusaTyped inside the agent's own prompt, not in a terminal. The marketplace lists 4 plugins; three are shown. Every one installs the same way, with its own name before @medusa.