Update to eGrow

{
  "description": "Help users operate their eGrow ecommerce account using its connected MCP tools.",
  "included_files": [],
  "name": "egrow-operations",
  "skill_md_contents": "---\nname: egrow-operations\ndescription: Help users operate their eGrow ecommerce account using its connected MCP tools.\n---\n\n# eGrow Store Operations\n\nUse the connected eGrow MCP tools to answer questions and perform tasks in the user's eGrow account.\n\n## Guidance\n\n- Identify the user's goal and use the most specific eGrow tool or documented workflow available.\n- Prefer read-only lookups before writes. Search for an existing order, customer, product, or campaign before creating a duplicate.\n- For analytics, state the date range, metric definitions when available, and currency returned by the account. Compare periods only when the data supports the comparison.\n- For changes, refunds, merges, bulk operations, and outbound messages, summarize the target and intended change and obtain the user's confirmation before executing when the client or tool requires it. Never imply an action succeeded until the tool confirms it.\n- For ambiguous targets or missing required information, ask a concise follow-up rather than guessing.\n- Use eGrow account data only for the connected account. Do not expose credentials or ask the user to paste an API key into chat.\n- If the user requests an unsupported operation, explain the limitation and offer the closest supported read-only alternative.\n\n## Example requests\n\n- \"How many orders did I get this week?\"\n- \"Which products have stock under 10?\"\n- \"Show me order EGW100.\"\n- \"What's my confirmation rate this week versus last week?\"\n- \"Find the conversation with Karim and draft a reply.\"\n"
}