Update to Gentoo

{
  "description": "Manage a Shopify store's Gentoo Growth Agent Goal, Opportunities, Actions, Tools, Performance, Credits, Conversations, and Shop settings using the Gentoo remote MCP tools.",
  "included_files": [],
  "name": "gentoo",
  "skill_md_contents": "---\nname: gentoo\ndescription: Manage a Shopify store's Gentoo Growth Agent Goal, Opportunities, Actions, Tools, Performance, Credits, Conversations, and Shop settings using the Gentoo remote MCP tools.\n---\n\n# Gentoo Merchant Skill\n\nUse this skill when the user wants to inspect or manage their Shopify store's Gentoo Growth Agent, including Store Goals, Opportunities, Action previews and approvals, current SEO requests, Goal performance (Overall and Week by week), Credit usage, Gentoo conversations, or Shop deploy settings.\n\n## Authentication and Setup\n\nThe user connects their store through the remote MCP OAuth flow (`https://mcp.gentooai.com/mcp`) using a one-time store connection key (`gt_pat_...`) generated in **Shopify Admin > Gentoo > Settings > Connectors**.\n\n- Never ask the user to paste passwords or Shopify Admin tokens in chat.\n- Every tool call is automatically scoped on the server to the authenticated Shopify store.\n\n## Core Operating Rules (Mandatory)\n\n1. **Two-Step Action Approval Protocol**:\n   - Never approve an Action (`gentoo_action_approve`) without first inspecting its preview.\n   - Step 1: Call `gentoo_action_preview` with `actionId` to retrieve the Before/After comparison states, screenshot capture URLs, credit cost, and `reviewFingerprint` (or `approvalViewFingerprint`).\n   - Step 2: Present the concrete Before/After summary and credit cost to the user and obtain explicit approval.\n   - Step 3: Only after explicit user confirmation, call `gentoo_action_approve` with `actionId` and `expectedReviewFingerprint`.\n2. **Preserve BIGINT Identifiers as Strings**:\n   - Always treat `blockerId`, `actionId`, `runId`, `jobId`, and `proposalId` as decimal strings. Never coerce them to floating-point numbers.\n3. **Confirmation Before Credit-Consuming or Storefront Writes**:\n   - Always obtain explicit user confirmation in the current task before calling write tools (`gentoo_action_approve`, `gentoo_action_rollback`, `gentoo_action_pause`, `gentoo_action_restore`, `gentoo_goal_propose`, `gentoo_goal_select`, or shop deploy-mode updates).\n"
}