[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M750RTGNSEN8K4DBMPCDJY41":3,"skill-same:01M750RTGNSEN8K4DBMPCDJY41":49},{"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},"01M750RTGNSEN8K4DBMPCDJY41","ideogram-incident-runbook",null,"Execute Ideogram incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Ideogram-related outages, investigating errors,\nor running post-incident reviews for Ideogram integration failures.\nTrigger with phrases like \"ideogram incident\", \"ideogram outage\",\n\"ideogram down\", \"ideogram on-call\", \"ideogram emergency\", \"ideogram broken\".","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\u002Fideogram-incident-runbook\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ideogram-incident-runbook\ndescription: |\n  Execute Ideogram incident response procedures with triage, mitigation, and postmortem.\n  Use when responding to Ideogram-related outages, investigating errors,\n  or running post-incident reviews for Ideogram integration failures.\n  Trigger with phrases like \"ideogram incident\", \"ideogram outage\",\n  \"ideogram down\", \"ideogram on-call\", \"ideogram emergency\", \"ideogram broken\".\nallowed-tools: Read, Grep, Bash(kubectl:*), Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Ideogram Incident Runbook\n\n## Overview\nRapid incident response procedures for Ideogram-related outages.\n\n## Prerequisites\n- Access to Ideogram dashboard and status page\n- kubectl access to production cluster\n- Prometheus\u002FGrafana access\n- Communication channels (Slack, PagerDuty)\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Complete outage | \u003C 15 min | Ideogram API unreachable |\n| P2 | Degraded service | \u003C 1 hour | High latency, partial failures |\n| P3 | Minor impact | \u003C 4 hours | Webhook delays, non-critical errors |\n| P4 | No user impact | Next business day | Monitoring gaps |\n\n## Quick Triage\n\n```bash\nset -euo pipefail\n# 1. Check Ideogram status\ncurl -s https:\u002F\u002Fstatus.ideogram.com | jq\n\n# 2. Check our integration health\ncurl -s https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.ideogram'\n\n# 3. Check error rate (last 5 min)\ncurl -s localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(ideogram_errors_total[5m])  # 9090: Prometheus port\n\n# 4. Recent error logs\nkubectl logs -l app=ideogram-integration --since=5m | grep -i error | tail -20\n```\n\n## Decision Tree\n\n```\nIdeogram API returning errors?\n├─ YES: Is status.ideogram.com showing incident?\n│   ├─ YES → Wait for Ideogram to resolve. Enable fallback.\n│   └─ NO → Our integration issue. Check credentials, config.\n└─ NO: Is our service healthy?\n    ├─ YES → Likely resolved or intermittent. Monitor.\n    └─ NO → Our infrastructure issue. Check pods, memory, network.\n```\n\n## Immediate Actions by Error Type\n\n### 401\u002F403 - Authentication\n```bash\nset -euo pipefail\n# Verify API key is set\nkubectl get secret ideogram-secrets -o jsonpath='{.data.api-key}' | base64 -d\n\n# Check if key was rotated\n# → Verify in Ideogram dashboard\n\n# Remediation: Update secret and restart pods\nkubectl create secret generic ideogram-secrets --from-literal=api-key=NEW_KEY --dry-run=client -o yaml | kubectl apply -f -\nkubectl rollout restart deployment\u002Fideogram-integration\n```\n\n### 429 - Rate Limited\n```bash\nset -euo pipefail\n# Check rate limit headers\ncurl -v https:\u002F\u002Fapi.ideogram.com 2>&1 | grep -i rate\n\n# Enable request queuing\nkubectl set env deployment\u002Fideogram-integration RATE_LIMIT_MODE=queue\n\n# Long-term: Contact Ideogram for limit increase\n```\n\n### 500\u002F503 - Ideogram Errors\n```bash\nset -euo pipefail\n# Enable graceful degradation\nkubectl set env deployment\u002Fideogram-integration IDEOGRAM_FALLBACK=true\n\n# Notify users of degraded service\n# Update status page\n\n# Monitor Ideogram status for resolution\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\n🔴 P1 INCIDENT: Ideogram Integration\nStatus: INVESTIGATING\nImpact: [Describe user impact]\nCurrent action: [What you're doing]\nNext update: [Time]\nIncident commander: @[name]\n```\n\n### External (Status Page)\n```\nIdeogram Integration Issue\n\nWe're experiencing issues with our Ideogram integration.\nSome users may experience [specific impact].\n\nWe're actively investigating and will provide updates.\n\nLast updated: [timestamp]\n```\n\n## Post-Incident\n\n### Evidence Collection\n```bash\nset -euo pipefail\n# Generate debug bundle\n.\u002Fscripts\u002Fideogram-debug-bundle.sh\n\n# Export relevant logs\nkubectl logs -l app=ideogram-integration --since=1h > incident-logs.txt\n\n# Capture metrics\ncurl \"localhost:9090\u002Fapi\u002Fv1\u002Fquery_range?query=ideogram_errors_total&start=2h\" > metrics.json  # 9090: Prometheus port\n```\n\n### Postmortem Template\n```markdown\n## Incident: Ideogram [Error Type]\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n\n### Summary\n[1-2 sentence description]\n\n### Timeline\n- HH:MM - [Event]\n- HH:MM - [Event]\n\n### Root Cause\n[Technical explanation]\n\n### Impact\n- Users affected: N\n- Revenue impact: $X\n\n### Action Items\n- [ ] [Preventive measure] - Owner - Due date\n```\n\n## Instructions\n\n### Step 1: Quick Triage\nRun the triage commands to identify the issue source.\n\n### Step 2: Follow Decision Tree\nDetermine if the issue is Ideogram-side or internal.\n\n### Step 3: Execute Immediate Actions\nApply the appropriate remediation for the error type.\n\n### Step 4: Communicate Status\nUpdate internal and external stakeholders.\n\n## Output\n- Issue identified and categorized\n- Remediation applied\n- Stakeholders notified\n- Evidence collected for postmortem\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't reach status page | Network issue | Use mobile or VPN |\n| kubectl fails | Auth expired | Re-authenticate |\n| Metrics unavailable | Prometheus down | Check backup metrics |\n| Secret rotation fails | Permission denied | Escalate to admin |\n\n## Examples\n\n### One-Line Health Check\n```bash\nset -euo pipefail\ncurl -sf https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.ideogram.status' || echo \"UNHEALTHY\"\n```\n\n## Resources\n- [Ideogram Status Page](https:\u002F\u002Fstatus.ideogram.com)\n- [Ideogram Support](https:\u002F\u002Fsupport.ideogram.com)\n\n## Next Steps\nFor data handling, see `ideogram-data-handling`.","# Ideogram Incident Runbook\n\n## Overview\nRapid incident response procedures for Ideogram-related outages.\n\n## Prerequisites\n- Access to Ideogram dashboard and status page\n- kubectl access to production cluster\n- Prometheus\u002FGrafana access\n- Communication channels (Slack, PagerDuty)\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Complete outage | \u003C 15 min | Ideogram API unreachable |\n| P2 | Degraded service | \u003C 1 hour | High latency, partial failures |\n| P3 | Minor impact | \u003C 4 hours | Webhook delays, non-critical errors |\n| P4 | No user impact | Next business day | Monitoring gaps |\n\n## Quick Triage\n\n```bash\nset -euo pipefail\n# 1. Check Ideogram status\ncurl -s https:\u002F\u002Fstatus.ideogram.com | jq\n\n# 2. Check our integration health\ncurl -s https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.ideogram'\n\n# 3. Check error rate (last 5 min)\ncurl -s localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(ideogram_errors_total[5m])  # 9090: Prometheus port\n\n# 4. Recent error logs\nkubectl logs -l app=ideogram-integration --since=5m | grep -i error | tail -20\n```\n\n## Decision Tree\n\n```\nIdeogram API returning errors?\n├─ YES: Is status.ideogram.com showing incident?\n│   ├─ YES → Wait for Ideogram to resolve. Enable fallback.\n│   └─ NO → Our integration issue. Check credentials, config.\n└─ NO: Is our service healthy?\n    ├─ YES → Likely resolved or intermittent. Monitor.\n    └─ NO → Our infrastructure issue. Check pods, memory, network.\n```\n\n## Immediate Actions by Error Type\n\n### 401\u002F403 - Authentication\n```bash\nset -euo pipefail\n# Verify API key is set\nkubectl get secret ideogram-secrets -o jsonpath='{.data.api-key}' | base64 -d\n\n# Check if key was rotated\n# → Verify in Ideogram dashboard\n\n# Remediation: Update secret and restart pods\nkubectl create secret generic ideogram-secrets --from-literal=api-key=NEW_KEY --dry-run=client -o yaml | kubectl apply -f -\nkubectl rollout restart deployment\u002Fideogram-integration\n```\n\n### 429 - Rate Limited\n```bash\nset -euo pipefail\n# Check rate limit headers\ncurl -v https:\u002F\u002Fapi.ideogram.com 2>&1 | grep -i rate\n\n# Enable request queuing\nkubectl set env deployment\u002Fideogram-integration RATE_LIMIT_MODE=queue\n\n# Long-term: Contact Ideogram for limit increase\n```\n\n### 500\u002F503 - Ideogram Errors\n```bash\nset -euo pipefail\n# Enable graceful degradation\nkubectl set env deployment\u002Fideogram-integration IDEOGRAM_FALLBACK=true\n\n# Notify users of degraded service\n# Update status page\n\n# Monitor Ideogram status for resolution\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\n🔴 P1 INCIDENT: Ideogram Integration\nStatus: INVESTIGATING\nImpact: [Describe user impact]\nCurrent action: [What you're doing]\nNext update: [Time]\nIncident commander: @[name]\n```\n\n### External (Status Page)\n```\nIdeogram Integration Issue\n\nWe're experiencing issues with our Ideogram integration.\nSome users may experience [specific impact].\n\nWe're actively investigating and will provide updates.\n\nLast updated: [timestamp]\n```\n\n## Post-Incident\n\n### Evidence Collection\n```bash\nset -euo pipefail\n# Generate debug bundle\n.\u002Fscripts\u002Fideogram-debug-bundle.sh\n\n# Export relevant logs\nkubectl logs -l app=ideogram-integration --since=1h > incident-logs.txt\n\n# Capture metrics\ncurl \"localhost:9090\u002Fapi\u002Fv1\u002Fquery_range?query=ideogram_errors_total&start=2h\" > metrics.json  # 9090: Prometheus port\n```\n\n### Postmortem Template\n```markdown\n## Incident: Ideogram [Error Type]\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n\n### Summary\n[1-2 sentence description]\n\n### Timeline\n- HH:MM - [Event]\n- HH:MM - [Event]\n\n### Root Cause\n[Technical explanation]\n\n### Impact\n- Users affected: N\n- Revenue impact: $X\n\n### Action Items\n- [ ] [Preventive measure] - Owner - Due date\n```\n\n## Instructions\n\n### Step 1: Quick Triage\nRun the triage commands to identify the issue source.\n\n### Step 2: Follow Decision Tree\nDetermine if the issue is Ideogram-side or internal.\n\n### Step 3: Execute Immediate Actions\nApply the appropriate remediation for the error type.\n\n### Step 4: Communicate Status\nUpdate internal and external stakeholders.\n\n## Output\n- Issue identified and categorized\n- Remediation applied\n- Stakeholders notified\n- Evidence collected for postmortem\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't reach status page | Network issue | Use mobile or VPN |\n| kubectl fails | Auth expired | Re-authenticate |\n| Metrics unavailable | Prometheus down | Check backup metrics |\n| Secret rotation fails | Permission denied | Escalate to admin |\n\n## Examples\n\n### One-Line Health Check\n```bash\nset -euo pipefail\ncurl -sf https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.ideogram.status' || echo \"UNHEALTHY\"\n```\n\n## Resources\n- [Ideogram Status Page](https:\u002F\u002Fstatus.ideogram.com)\n- [Ideogram Support](https:\u002F\u002Fsupport.ideogram.com)\n\n## Next Steps\nFor data handling, see `ideogram-data-handling`.",{"name":5,"author":24,"license":15,"version":25,"description":26,"allowed-tools":27,"compatible-with":28},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Ideogram incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Ideogram-related outages, investigating errors,\nor running post-incident reviews for Ideogram integration failures.\nTrigger with phrases like \"ideogram incident\", \"ideogram outage\",\n\"ideogram down\", \"ideogram on-call\", \"ideogram emergency\", \"ideogram broken\".\n","Read, Grep, Bash(kubectl:*), 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 ideogram-incident-runbook",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill ideogram-incident-runbook",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill ideogram-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fideogram-incident-runbook\u002FSKILL.md",true,[],[50,57,64,71,78,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]