
Medusa Agent Skills
https://github.com/medusajs/medusa-agent-skills- Category
- AI Agents
- Rank
- No. 652Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- medusajs
- GitHub
- 215 stars
- Latest release
- 1.0.7
- Date
About
Claude Code skills and commands that encode Medusa best practices so agents build ecommerce features the Medusa way.
What it does
Medusa Agent Skills packages four focused assistants: application development, a guided brands tutorial, storefront design, and Medusa Cloud operations. Agents receive local instructional material, while selected plugins can query public Medusa documentation through an MCP server. Storefront guidance also works with ecommerce backends other than Medusa.
Why it's ranked here
The collection covers an unusually complete Medusa workflow, from learning architecture through backend, admin, storefront, and cloud work. Its maintenance tooling adds confidence by checking manifests, skill metadata, duplicate names, JSON, and relative links. The main caveat is portability: copying skills to another agent does not automatically bring the documentation server.
What's good
The scope is concrete. Backend guidance covers modules, workflows, routes, and migrations. Admin guidance includes widgets, pages, forms, React Query, and Medusa UI components. The tutorial uses checkpoints and verification while building a real brands feature. Cloud skills divide authentication, deployments, logs, environments, variables, projects, organizations, and local build reproduction into distinct tasks.
Tradeoffs
The richest installation path targets Claude Code. Other agents can copy skills, but the documented installer cannot copy the MCP server, so that configuration is manual. The learning plugin teaches through one prescribed brands feature rather than an open curriculum. Storefront advice covers UX, conversion, SEO, responsiveness, and integration, but it is guidance for an existing or planned project, not an ecommerce backend.
How to use it well
Use it when an agent is actively building or teaching a Medusa application, especially work spanning backend modules, admin extensions, storefront integration, migrations, or Cloud CLI operations. Install only the plugin matching the task. Pair the tutorial with hands-on coding and its checkpoints. For non-Claude agents, copy the skills and configure documentation access separately. Do not treat it as the application runtime, hosting platform, or ecommerce backend itself.
Technical notes+
.claude-plugin/marketplace.json registers four plugin sources. plugins/medusa-dev/.mcp.json and plugins/learn-medusa/.mcp.json configure the HTTP MedusaDocs server at https://docs.medusajs.com/mcp. scripts/validate-skills.mjs parses every JSON file, verifies marketplace sources and manifests, enforces YAML frontmatter and unique kebab-case skill names, and resolves relative Markdown links. scripts/bump-versions.mjs increments changed plugin patch versions and the marketplace version. scripts/resolve-docs-commit.mjs filters documentation changes and bounds attached patches. scripts/skills-stats-to-posthog.mjs discovers skill directories, reads install counts from skills.sh, and sends snapshots to PostHog. The repository explicitly has no package.json, so its validation script substitutes for lint, build, and test commands.
Observed
- Packaging
- Claude Code marketplace containing four independently installable plugins.
- Install surfaces
- Claude Code plugin commands, the skills package runner, or manual copying for other agents.
- Interfaces
- Local agent skills, Claude Code commands, an HTTP MCP documentation server, and Medusa Cloud CLI guidance.
- Agent support
- Designed for Claude Code; documented use with other agents includes Cursor.
- Automation language
- Repository maintenance and telemetry scripts use JavaScript ES modules on Node.js.
- Privacy statement
- Plugin instructions are local, and configured MCP servers query only public Medusa documentation.
- Project structure
- No package.json; a repository integrity script stands in for lint, build, and test commands.
Read from README.md, scripts/bump-versions.mjs, scripts/validate-skills.mjs, scripts/resolve-docs-commit.mjs, scripts/skills-stats-to-posthog.mjs, .claude-plugin/marketplace.json, plugins/medusa-dev/.mcp.json, plugins/medusa-dev/README.md, plugins/learn-medusa/.mcp.json, plugins/learn-medusa/README.md, plugins/medusa-cloud/README.md, plugins/ecommerce-storefront/README.md, .github/prompts/sync-medusa-docs-changes.md, .github/workflows/skills-stats-to-posthog.yml, .github/workflows/sync-medusa-docs-changes.yml.
What it can do
Generate Medusa ecommerce API endpoints
Feature requirements and specifications → API endpoint code following Medusa patterns
Create Medusa service classes
Business logic requirements → Service class code with Medusa best practices
Build Medusa entity models
Data structure requirements → Entity model code with proper Medusa schema
Generate Medusa migration files
Database schema changes → Migration scripts following Medusa conventions
Create Medusa middleware components
Request handling requirements → Middleware code with Medusa integration patterns
Build Medusa plugin structure
Plugin functionality specifications → Complete plugin code with Medusa architecture
Tags
Media

Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.