Medusa headless commerce - modules, workflows, API routes, admin UI
51
64%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./skills/medusa/SKILL.mdThe skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The prompt contains explicit example secrets (database URL with password, JWT_SECRET/COOKIE_SECRET placeholders, sample user passwords like "supersecret"/"password123") and shows passing passwords as CLI arguments (e.g., `npx medusa user -p ...`), which would require the LLM to include secret values verbatim and is high-risk.
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
The skill explicitly includes payment gateway integration: it documents installing and configuring the @medusajs/payment-stripe module and shows adding Stripe as a payment provider (with an STRIPE_API_KEY). It also exposes endpoints/workflows to complete carts and create orders. Because it specifically integrates a payment gateway (Stripe) and configuration to send payment transactions, it provides direct financial execution capability.
alinaqi/maggy
55aabe2
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.