{"id":98783,"plugin_id":"plugin_asdk_app_6accf624ea808191980d359c299fae66","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-16T18:15:27.405Z","digest":"97551c7ee987c5034b18485edd69910f92cbb0e6b526cefdb2c520a4473281d1","against":null,"payload":{"description":"Connecting the MWM AI plugin to an MWM account and getting its tools working, then the App Store Connect and Google Play connections a task needs, set up in MWM Console. Use when the person says things like \"connect MWM AI\", \"the MWM tools are missing\", \"I get an authorization error\", \"connect my App Store account\" or \"is my Google Play connected?\". Not for what the assistant may do once connected (working-with-mwm).","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":203}],"name":"setup","skill_md_contents":"---\nname: setup\ndescription: \"Connecting the MWM AI plugin to an MWM account and getting its tools working, then the App Store Connect and Google Play connections a task needs, set up in MWM Console. Use when the person says things like \\\"connect MWM AI\\\", \\\"the MWM tools are missing\\\", \\\"I get an authorization error\\\", \\\"connect my App Store account\\\" or \\\"is my Google Play connected?\\\". Not for what the assistant may do once connected (working-with-mwm).\"\n---\n\n# Set up MWM AI\n\n## When this applies\n\nRight after installation, whenever MWM's tools are missing or fail to authenticate, and when the person wants a store account connected to MWM. What the assistant may do once everything is connected belongs to working-with-mwm.\n\n## The job and what good looks like\n\nThe person ends with MWM's tools working in their host, the store connections their task needs in place, and their original task resumed. Installing the plugin adds its skills; connecting the MWM account is a separate sign-in in the browser, and signing in to MWM Console alone does not connect the plugin. Access is reported as working only after a successful read: `get_publishing_knowledge` answers any store question for free, without a store connection or an app, and proves the tools respond.\n\n## How a pro decides\n\n- **Which of three problems.** No MWM tools means the MCP connection is missing. A store that is not connected means MWM Console needs that store's account. An act refused while the tools work means the person's role or organization lacks the right. Each has its own fix.\n- **Missing tools after a sign-in.** Check that the plugin is enabled, refresh the host's tool list, or open a new chat.\n- **Authorization or an expired session.** Use the host's reconnect or Authenticate control and check again.\n- **A connection without MWM's tools.** The MCP has one permission: reconnect MWM in the host to grant it.\n- **A network or server error.** Report it as it came: signing in again does not fix an endpoint that cannot be reached.\n\n## Do\n\n- In Codex desktop, open Settings and MCP servers, select Authenticate for MWM AI, sign in and consent in the browser, come back, and restart the server or open a new chat.\n- When the plugin's server is absent there, check that MWM AI is installed and enabled. Only when no MWM server works, add one by hand: Streamable HTTP, URL `https://mcp.mwm.ai/mcp`, and authenticate it.\n- In Claude Code, open the MCP panel with the mcp slash command, choose MWM AI and authenticate.\n- For a store, send the person to the store connections of MWM Console, where the account is connected in their browser, and check again once they are back.\n- Resume the person's original task as soon as access works.\n- If a secret is pasted in the chat, don't repeat it; advise revoking it with its issuer and connecting a new one through MWM Console.\n\n## Don't\n\n- Don't ask for passwords, API keys, private key files, service account JSON, one-time codes or browser callback URLs.\n- Don't guess a menu path in a host whose interface you don't know; say what to look for instead.\n- Don't generate, connect or publish anything to test the connection.\n- Don't read a store connection as permission to write or publish.\n\n## Pitfalls\n\n- Sending someone to MWM Console's consent page directly does not start a sign-in: the host has to create the request.\n- A missing MCP connection says nothing about whether a store is connected.\n- Two servers for the same endpoint confuse the host.\n\n## Store facts\n\nTool results carry the store rules and limits they depend on, each with its source and the date it was checked. `get_publishing_knowledge` answers questions on this skill's topics the same way (topics: `mwm/store-connections`). When you use one of these facts, give its source and date.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}