[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74WFASJS4YS4ZPZCM7F9K93":3,"skill-same:01M74WFASJS4YS4ZPZCM7F9K93":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M74WFASJS4YS4ZPZCM7F9K93","customerio-common-errors",null,"Diagnose and fix Customer.io common errors.\nUse when troubleshooting API errors, delivery issues,\nor integration problems with Customer.io.\nTrigger with phrases like \"customer.io error\", \"customer.io not working\",\n\"debug customer.io\", \"customer.io issue\".","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fcustomerio-common-errors\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: customerio-common-errors\ndescription: |\n  Diagnose and fix Customer.io common errors.\n  Use when troubleshooting API errors, delivery issues,\n  or integration problems with Customer.io.\n  Trigger with phrases like \"customer.io error\", \"customer.io not working\",\n  \"debug customer.io\", \"customer.io issue\".\nallowed-tools: Read, Grep, Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Customer.io Common Errors\n\n## Overview\nDiagnose and resolve common Customer.io integration errors, delivery issues, and API problems.\n\n## Prerequisites\n- Access to Customer.io dashboard\n- API credentials configured\n- Access to application logs\n\n## Error Reference\n\n| Error Code | Meaning | Action |\n|------------|---------|--------|\n| 400 | Bad Request | Check request format and data |\n| 401 | Unauthorized | Verify API credentials |\n| 403 | Forbidden | Check API key permissions |\n| 404 | Not Found | Verify endpoint URL |\n| 429 | Rate Limited | Implement backoff |\n| 500 | Server Error | Retry with backoff |\n\n## Instructions\n\n### Step 1: Identify the Error Category\nCheck error response code and message. Authentication errors (401\u002F403) need credential review. Request errors (400) need payload fixes. Rate limits (429) need backoff logic.\n\n### Step 2: Fix Authentication Issues\nVerify correct API key type (Track vs App). Check environment variables are loaded. Ensure credentials match the workspace.\n\n### Step 3: Fix Request Errors\nCheck for empty user IDs, millisecond timestamps (use Unix seconds), and malformed email addresses. Validate payloads before sending.\n\n### Step 4: Handle Rate Limiting\nImplement exponential backoff with jitter. Start at 1s delay and double on each retry. Skip retries on 4xx errors (except 429).\n\n### Step 5: Debug Delivery Issues\nCheck user activity in dashboard, verify campaign is active and user matches segment, review suppression list, and check message preview.\n\n### Step 6: Fix SDK-Specific Errors\nFor Node.js, check env vars exist before creating client. For Python, catch both `CustomerIOError` and `ConnectionError`.\n\nFor detailed code examples and diagnostic commands, load the reference guide:\n`Read(${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation-guide.md)`\n\n## Diagnostic Commands\n```bash\nset -euo pipefail\n# Check API connectivity\ncurl -X POST \"https:\u002F\u002Ftrack.customer.io\u002Fapi\u002Fv1\u002Fcustomers\u002Ftest-user\" \\\n  -u \"$CUSTOMERIO_SITE_ID:$CUSTOMERIO_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"email\":\"test@example.com\"}' \\\n  -w \"\\nHTTP Status: %{http_code}\\n\"\n```\n\n## Error Handling\n| Issue | Solution |\n|-------|----------|\n| Events not triggering campaigns | Check exact event name (case-sensitive) |\n| User not in segment | Verify required attributes and types |\n| SDK initialization error | Check env vars exist before creating client |\n\n## Resources\n- [API Error Reference](https:\u002F\u002Fcustomer.io\u002Fdocs\u002Fapi\u002Ftrack\u002F#section\u002FErrors)\n- [Troubleshooting Guide](https:\u002F\u002Fcustomer.io\u002Fdocs\u002Ftroubleshooting\u002F)\n- [Status Page](https:\u002F\u002Fstatus.customer.io\u002F)\n\n## Next Steps\nAfter resolving errors, proceed to `customerio-debug-bundle` for comprehensive debug reports.\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale\n\nSee [debugging implementation details](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for output format specifications.\n\n## Examples\n\n**Basic usage**: Apply customerio common errors to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize customerio common errors for production environments with multiple constraints and team-specific requirements.","# Customer.io Common Errors\n\n## Overview\nDiagnose and resolve common Customer.io integration errors, delivery issues, and API problems.\n\n## Prerequisites\n- Access to Customer.io dashboard\n- API credentials configured\n- Access to application logs\n\n## Error Reference\n\n| Error Code | Meaning | Action |\n|------------|---------|--------|\n| 400 | Bad Request | Check request format and data |\n| 401 | Unauthorized | Verify API credentials |\n| 403 | Forbidden | Check API key permissions |\n| 404 | Not Found | Verify endpoint URL |\n| 429 | Rate Limited | Implement backoff |\n| 500 | Server Error | Retry with backoff |\n\n## Instructions\n\n### Step 1: Identify the Error Category\nCheck error response code and message. Authentication errors (401\u002F403) need credential review. Request errors (400) need payload fixes. Rate limits (429) need backoff logic.\n\n### Step 2: Fix Authentication Issues\nVerify correct API key type (Track vs App). Check environment variables are loaded. Ensure credentials match the workspace.\n\n### Step 3: Fix Request Errors\nCheck for empty user IDs, millisecond timestamps (use Unix seconds), and malformed email addresses. Validate payloads before sending.\n\n### Step 4: Handle Rate Limiting\nImplement exponential backoff with jitter. Start at 1s delay and double on each retry. Skip retries on 4xx errors (except 429).\n\n### Step 5: Debug Delivery Issues\nCheck user activity in dashboard, verify campaign is active and user matches segment, review suppression list, and check message preview.\n\n### Step 6: Fix SDK-Specific Errors\nFor Node.js, check env vars exist before creating client. For Python, catch both `CustomerIOError` and `ConnectionError`.\n\nFor detailed code examples and diagnostic commands, load the reference guide:\n`Read(${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation-guide.md)`\n\n## Diagnostic Commands\n```bash\nset -euo pipefail\n# Check API connectivity\ncurl -X POST \"https:\u002F\u002Ftrack.customer.io\u002Fapi\u002Fv1\u002Fcustomers\u002Ftest-user\" \\\n  -u \"$CUSTOMERIO_SITE_ID:$CUSTOMERIO_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"email\":\"test@example.com\"}' \\\n  -w \"\\nHTTP Status: %{http_code}\\n\"\n```\n\n## Error Handling\n| Issue | Solution |\n|-------|----------|\n| Events not triggering campaigns | Check exact event name (case-sensitive) |\n| User not in segment | Verify required attributes and types |\n| SDK initialization error | Check env vars exist before creating client |\n\n## Resources\n- [API Error Reference](https:\u002F\u002Fcustomer.io\u002Fdocs\u002Fapi\u002Ftrack\u002F#section\u002FErrors)\n- [Troubleshooting Guide](https:\u002F\u002Fcustomer.io\u002Fdocs\u002Ftroubleshooting\u002F)\n- [Status Page](https:\u002F\u002Fstatus.customer.io\u002F)\n\n## Next Steps\nAfter resolving errors, proceed to `customerio-debug-bundle` for comprehensive debug reports.\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale\n\nSee [debugging implementation details](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for output format specifications.\n\n## Examples\n\n**Basic usage**: Apply customerio common errors to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize customerio common errors for production environments with multiple constraints and team-specific requirements.",{"name":5,"author":24,"license":15,"version":25,"description":26,"allowed-tools":27,"compatible-with":28},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Diagnose and fix Customer.io common errors.\nUse when troubleshooting API errors, delivery issues,\nor integration problems with Customer.io.\nTrigger with phrases like \"customer.io error\", \"customer.io not working\",\n\"debug customer.io\", \"customer.io issue\".\n","Read, Grep, Bash(curl:*)","claude-code, codex, openclaw","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill customerio-common-errors",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill customerio-common-errors",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill customerio-common-errors","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fcustomerio-common-errors\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fimplementation-guide.md","REFERENCE","参考文档",4775,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fcustomerio-common-errors\u002Freferences\u002Fimplementation-guide.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fimplementation.md",3770,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fcustomerio-common-errors\u002Freferences\u002Fimplementation.md",[60,67,74,81,88,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]