[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F6F4AZFX4SNF8AQ03VESVR":3,"skill-same:01M6F6F4AZFX4SNF8AQ03VESVR":83},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6F6F4AZFX4SNF8AQ03VESVR","adobe-incident-runbook",null,"Execute Adobe incident response procedures with triage, mitigation,\nand postmortem for Firefly Services, PDF Services, and I\u002FO Events outages.\nUse when responding to Adobe-related incidents, investigating API failures,\nor running post-incident reviews.\nTrigger with phrases like \"adobe incident\", \"adobe outage\",\n\"adobe down\", \"adobe on-call\", \"adobe emergency\".","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",67,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fjeremylongshore\u002Fclaude-code-plugins-plus-skills\u002Fadobe-incident-runbook\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"adobe incident runbook","adobe","runbook","incident","read","with","events","trigger","io","call","use","PDF","postmortem","Bash","api","saas","kubectl","code","incident response","design","2026-11-10 10:12:30",false,"---\nname: adobe-incident-runbook\ndescription: |\n  Execute Adobe incident response procedures with triage, mitigation,\n  and postmortem for Firefly Services, PDF Services, and I\u002FO Events outages.\n  Use when responding to Adobe-related incidents, investigating API failures,\n  or running post-incident reviews.\n  Trigger with phrases like \"adobe incident\", \"adobe outage\",\n  \"adobe down\", \"adobe on-call\", \"adobe emergency\".\nallowed-tools: Read, Grep, Bash(kubectl:*), Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, design, adobe]\ncompatible-with: claude-code\n---\n\n# Adobe Incident Runbook\n\n## Overview\n\nRapid incident response procedures for Adobe API-related outages, covering IMS authentication failures, Firefly\u002FPhotoshop API downtime, PDF Services quota exhaustion, and I\u002FO Events delivery failures.\n\n## Prerequisites\n\n- Access to Adobe Developer Console and Admin Console\n- Access to application monitoring (Grafana, Datadog, etc.)\n- kubectl access to production cluster (if applicable)\n- Communication channels (Slack, PagerDuty)\n\n## Severity Matrix\n\n| Level | Definition | Response Time | Example |\n|-------|------------|---------------|---------|\n| P1 | Complete Adobe integration failure | \u003C 15 min | IMS auth broken, all APIs down |\n| P2 | Single API degraded | \u003C 1 hour | Firefly 429s, Photoshop timeouts |\n| P3 | Minor impact | \u003C 4 hours | Webhook delays, slow PDF extraction |\n| P4 | No user impact | Next business day | Monitoring gap, metric anomaly |\n\n## Quick Triage (Run These First)\n\n```bash\n# 1. Is Adobe itself down?\ncurl -s -o \u002Fdev\u002Fnull -w \"Adobe Status: %{http_code}\\n\" https:\u002F\u002Fstatus.adobe.com\n\n# 2. Can we generate an access token?\ncurl -s -o \u002Fdev\u002Fnull -w \"IMS Auth: %{http_code}\\n\" -X POST \\\n  'https:\u002F\u002Fims-na1.adobelogin.com\u002Fims\u002Ftoken\u002Fv3' \\\n  -d \"client_id=${ADOBE_CLIENT_ID}&client_secret=${ADOBE_CLIENT_SECRET}&grant_type=client_credentials&scope=${ADOBE_SCOPES}\"\n\n# 3. Can we reach each API endpoint?\nfor endpoint in firefly-api.adobe.io image.adobe.io pdf-services.adobe.io; do\n  CODE=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" --connect-timeout 5 \"https:\u002F\u002F$endpoint\" 2>\u002Fdev\u002Fnull || echo \"UNREACHABLE\")\n  echo \"$endpoint: $CODE\"\ndone\n\n# 4. Check our app health\ncurl -sf https:\u002F\u002Fyour-app.com\u002Fhealth | python3 -m json.tool\n\n# 5. Recent errors in our logs (last 5 min)\nkubectl logs -l app=adobe-service --since=5m 2>\u002Fdev\u002Fnull | grep -i \"error\\|failed\\|429\\|401\\|500\" | tail -20\n```\n\n## Decision Tree\n\n```\nAdobe APIs returning errors?\n├── YES: Is status.adobe.com reporting an incident?\n│   ├── YES → Adobe-side outage. Enable fallback mode. Monitor status page.\n│   └── NO → Check our credentials and config.\n│       ├── 401 errors → Credentials expired\u002Frotated. See \"Auth Recovery\" below.\n│       ├── 429 errors → Rate limited. See \"Rate Limit Recovery\" below.\n│       └── 500\u002F503 errors → Adobe server issue (unreported). Open support ticket.\n└── NO: Is our application healthy?\n    ├── YES → Likely resolved or intermittent. Continue monitoring.\n    └── NO → Our infrastructure issue. Check pods, memory, network.\n```\n\n## Recovery Procedures\n\n### Auth Recovery (401\u002F403)\n\n```bash\n# 1. Verify credentials are still valid in Developer Console\n#    https:\u002F\u002Fdeveloper.adobe.com\u002Fconsole → Your Project → Credentials\n\n# 2. Test credential directly\ncurl -v -X POST 'https:\u002F\u002Fims-na1.adobelogin.com\u002Fims\u002Ftoken\u002Fv3' \\\n  -d \"client_id=${ADOBE_CLIENT_ID}&client_secret=${ADOBE_CLIENT_SECRET}&grant_type=client_credentials&scope=${ADOBE_SCOPES}\" 2>&1 | grep -E \"HTTP|error\"\n\n# 3. If credentials were rotated, update in secret manager\ngcloud secrets versions add adobe-client-secret --data-file=- \u003C\u003C\u003C \"new_p8_secret\"\n# OR\naws secretsmanager update-secret --secret-id adobe\u002Fproduction\u002Fcredentials \\\n  --secret-string '{\"client_id\":\"...\",\"client_secret\":\"new_secret\"}'\n\n# 4. Restart application to clear cached token\nkubectl rollout restart deployment\u002Fadobe-service\n\n# 5. Verify recovery\ncurl -sf https:\u002F\u002Fyour-app.com\u002Fhealth | jq '.services.adobe'\n```\n\n### Rate Limit Recovery (429)\n\n```bash\n# 1. Check if rate limiting is transient or sustained\n# Look at 429 error rate over last 30 min\n\n# 2. Reduce throughput immediately\n# Option A: Scale down workers\nkubectl scale deployment\u002Fadobe-batch-worker --replicas=1\n\n# Option B: Enable rate limit queue mode\nkubectl set env deployment\u002Fadobe-service ADOBE_RATE_LIMIT_MODE=queue\n\n# 3. For sustained rate limiting, contact Adobe for limit increase\n# Include: client_id, typical request volume, business justification\n```\n\n### Fallback Mode\n\n```bash\n# Enable fallback mode (app continues working without Adobe)\nkubectl set env deployment\u002Fadobe-service ADOBE_FALLBACK_MODE=true\n\n# Verify fallback is working\ncurl -sf https:\u002F\u002Fyour-app.com\u002Fhealth | jq '.services.adobe'\n# Should return { \"status\": \"degraded\", \"mode\": \"fallback\" }\n```\n\n## Communication Templates\n\n### Internal (Slack)\n\n```\nP[1-4] INCIDENT: Adobe [API Name] Integration\nStatus: INVESTIGATING \u002F IDENTIFIED \u002F MONITORING \u002F RESOLVED\nImpact: [User-facing description]\nRoot cause: [Adobe outage \u002F credential issue \u002F rate limit \u002F our bug]\nCurrent action: [What you're doing right now]\nNext update: [Time]\nCommander: @[name]\n```\n\n### Postmortem Template\n\n```markdown\n## Incident: Adobe [API] [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 of what happened]\n\n### Timeline\n- HH:MM UTC — Alert fired: adobe_api_errors_total spike\n- HH:MM UTC — On-call acknowledged, began triage\n- HH:MM UTC — Root cause identified: [description]\n- HH:MM UTC — Mitigation applied: [action taken]\n- HH:MM UTC — Full recovery confirmed\n\n### Root Cause\n[Technical explanation — was it Adobe-side, credential issue, our bug?]\n\n### Impact\n- Users affected: N\n- API calls failed: N\n- Revenue impact: $X (if applicable)\n\n### Action Items\n- [ ] [Preventive measure] — Owner — Due date\n- [ ] [Monitoring improvement] — Owner — Due date\n- [ ] [Documentation update] — Owner — Due date\n```\n\n## Output\n\n- Incident severity classified\n- Root cause identified via decision tree\n- Recovery procedure executed\n- Stakeholders notified with template\n- Evidence collected for postmortem\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't reach status.adobe.com | Network issue | Use mobile data or check @AdobeCare on Twitter |\n| kubectl auth expired | Token timeout | Re-authenticate with cloud provider |\n| Secret manager access denied | IAM policy | Use break-glass admin account |\n| Fallback mode not implemented | Missing code path | Return cached\u002Fdefault data |\n\n## Resources\n\n- [Adobe Status Page](https:\u002F\u002Fstatus.adobe.com)\n- [Adobe Developer Support](https:\u002F\u002Fdeveloper.adobe.com\u002Fsupport)\n- [Adobe Developer Console](https:\u002F\u002Fdeveloper.adobe.com\u002Fconsole)\n\n## Next Steps\n\nFor data handling, see `adobe-data-handling`.\n\n","# Adobe Incident Runbook\n\n## Overview\n\nRapid incident response procedures for Adobe API-related outages, covering IMS authentication failures, Firefly\u002FPhotoshop API downtime, PDF Services quota exhaustion, and I\u002FO Events delivery failures.\n\n## Prerequisites\n\n- Access to Adobe Developer Console and Admin Console\n- Access to application monitoring (Grafana, Datadog, etc.)\n- kubectl access to production cluster (if applicable)\n- Communication channels (Slack, PagerDuty)\n\n## Severity Matrix\n\n| Level | Definition | Response Time | Example |\n|-------|------------|---------------|---------|\n| P1 | Complete Adobe integration failure | \u003C 15 min | IMS auth broken, all APIs down |\n| P2 | Single API degraded | \u003C 1 hour | Firefly 429s, Photoshop timeouts |\n| P3 | Minor impact | \u003C 4 hours | Webhook delays, slow PDF extraction |\n| P4 | No user impact | Next business day | Monitoring gap, metric anomaly |\n\n## Quick Triage (Run These First)\n\n```bash\n# 1. Is Adobe itself down?\ncurl -s -o \u002Fdev\u002Fnull -w \"Adobe Status: %{http_code}\\n\" https:\u002F\u002Fstatus.adobe.com\n\n# 2. Can we generate an access token?\ncurl -s -o \u002Fdev\u002Fnull -w \"IMS Auth: %{http_code}\\n\" -X POST \\\n  'https:\u002F\u002Fims-na1.adobelogin.com\u002Fims\u002Ftoken\u002Fv3' \\\n  -d \"client_id=${ADOBE_CLIENT_ID}&client_secret=${ADOBE_CLIENT_SECRET}&grant_type=client_credentials&scope=${ADOBE_SCOPES}\"\n\n# 3. Can we reach each API endpoint?\nfor endpoint in firefly-api.adobe.io image.adobe.io pdf-services.adobe.io; do\n  CODE=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" --connect-timeout 5 \"https:\u002F\u002F$endpoint\" 2>\u002Fdev\u002Fnull || echo \"UNREACHABLE\")\n  echo \"$endpoint: $CODE\"\ndone\n\n# 4. Check our app health\ncurl -sf https:\u002F\u002Fyour-app.com\u002Fhealth | python3 -m json.tool\n\n# 5. Recent errors in our logs (last 5 min)\nkubectl logs -l app=adobe-service --since=5m 2>\u002Fdev\u002Fnull | grep -i \"error\\|failed\\|429\\|401\\|500\" | tail -20\n```\n\n## Decision Tree\n\n```\nAdobe APIs returning errors?\n├── YES: Is status.adobe.com reporting an incident?\n│   ├── YES → Adobe-side outage. Enable fallback mode. Monitor status page.\n│   └── NO → Check our credentials and config.\n│       ├── 401 errors → Credentials expired\u002Frotated. See \"Auth Recovery\" below.\n│       ├── 429 errors → Rate limited. See \"Rate Limit Recovery\" below.\n│       └── 500\u002F503 errors → Adobe server issue (unreported). Open support ticket.\n└── NO: Is our application healthy?\n    ├── YES → Likely resolved or intermittent. Continue monitoring.\n    └── NO → Our infrastructure issue. Check pods, memory, network.\n```\n\n## Recovery Procedures\n\n### Auth Recovery (401\u002F403)\n\n```bash\n# 1. Verify credentials are still valid in Developer Console\n#    https:\u002F\u002Fdeveloper.adobe.com\u002Fconsole → Your Project → Credentials\n\n# 2. Test credential directly\ncurl -v -X POST 'https:\u002F\u002Fims-na1.adobelogin.com\u002Fims\u002Ftoken\u002Fv3' \\\n  -d \"client_id=${ADOBE_CLIENT_ID}&client_secret=${ADOBE_CLIENT_SECRET}&grant_type=client_credentials&scope=${ADOBE_SCOPES}\" 2>&1 | grep -E \"HTTP|error\"\n\n# 3. If credentials were rotated, update in secret manager\ngcloud secrets versions add adobe-client-secret --data-file=- \u003C\u003C\u003C \"new_p8_secret\"\n# OR\naws secretsmanager update-secret --secret-id adobe\u002Fproduction\u002Fcredentials \\\n  --secret-string '{\"client_id\":\"...\",\"client_secret\":\"new_secret\"}'\n\n# 4. Restart application to clear cached token\nkubectl rollout restart deployment\u002Fadobe-service\n\n# 5. Verify recovery\ncurl -sf https:\u002F\u002Fyour-app.com\u002Fhealth | jq '.services.adobe'\n```\n\n### Rate Limit Recovery (429)\n\n```bash\n# 1. Check if rate limiting is transient or sustained\n# Look at 429 error rate over last 30 min\n\n# 2. Reduce throughput immediately\n# Option A: Scale down workers\nkubectl scale deployment\u002Fadobe-batch-worker --replicas=1\n\n# Option B: Enable rate limit queue mode\nkubectl set env deployment\u002Fadobe-service ADOBE_RATE_LIMIT_MODE=queue\n\n# 3. For sustained rate limiting, contact Adobe for limit increase\n# Include: client_id, typical request volume, business justification\n```\n\n### Fallback Mode\n\n```bash\n# Enable fallback mode (app continues working without Adobe)\nkubectl set env deployment\u002Fadobe-service ADOBE_FALLBACK_MODE=true\n\n# Verify fallback is working\ncurl -sf https:\u002F\u002Fyour-app.com\u002Fhealth | jq '.services.adobe'\n# Should return { \"status\": \"degraded\", \"mode\": \"fallback\" }\n```\n\n## Communication Templates\n\n### Internal (Slack)\n\n```\nP[1-4] INCIDENT: Adobe [API Name] Integration\nStatus: INVESTIGATING \u002F IDENTIFIED \u002F MONITORING \u002F RESOLVED\nImpact: [User-facing description]\nRoot cause: [Adobe outage \u002F credential issue \u002F rate limit \u002F our bug]\nCurrent action: [What you're doing right now]\nNext update: [Time]\nCommander: @[name]\n```\n\n### Postmortem Template\n\n```markdown\n## Incident: Adobe [API] [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 of what happened]\n\n### Timeline\n- HH:MM UTC — Alert fired: adobe_api_errors_total spike\n- HH:MM UTC — On-call acknowledged, began triage\n- HH:MM UTC — Root cause identified: [description]\n- HH:MM UTC — Mitigation applied: [action taken]\n- HH:MM UTC — Full recovery confirmed\n\n### Root Cause\n[Technical explanation — was it Adobe-side, credential issue, our bug?]\n\n### Impact\n- Users affected: N\n- API calls failed: N\n- Revenue impact: $X (if applicable)\n\n### Action Items\n- [ ] [Preventive measure] — Owner — Due date\n- [ ] [Monitoring improvement] — Owner — Due date\n- [ ] [Documentation update] — Owner — Due date\n```\n\n## Output\n\n- Incident severity classified\n- Root cause identified via decision tree\n- Recovery procedure executed\n- Stakeholders notified with template\n- Evidence collected for postmortem\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Can't reach status.adobe.com | Network issue | Use mobile data or check @AdobeCare on Twitter |\n| kubectl auth expired | Token timeout | Re-authenticate with cloud provider |\n| Secret manager access denied | IAM policy | Use break-glass admin account |\n| Fallback mode not implemented | Missing code path | Return cached\u002Fdefault data |\n\n## Resources\n\n- [Adobe Status Page](https:\u002F\u002Fstatus.adobe.com)\n- [Adobe Developer Support](https:\u002F\u002Fdeveloper.adobe.com\u002Fsupport)\n- [Adobe Developer Console](https:\u002F\u002Fdeveloper.adobe.com\u002Fconsole)\n\n## Next Steps\n\nFor data handling, see `adobe-data-handling`.\n\n",{"name":5,"tags":54,"author":55,"license":15,"version":56,"description":57,"allowed-tools":58,"compatible-with":59},[44,48,30],"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Adobe incident response procedures with triage, mitigation,\nand postmortem for Firefly Services, PDF Services, and I\u002FO Events outages.\nUse when responding to Adobe-related incidents, investigating API failures,\nor running post-incident reviews.\nTrigger with phrases like \"adobe incident\", \"adobe outage\",\n\"adobe down\", \"adobe on-call\", \"adobe emergency\".\n","Read, Grep, Bash(kubectl:*), Bash(curl:*)","claude-code","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Fjeremylongshore\u002Fclaude-code-plugins-plus-skills\u002Fadobe-incident-runbook",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill adobe-incident-runbook",{"tool":75,"command":76},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill adobe-incident-runbook",{"tool":78,"command":79},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill adobe-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fjeremylongshore\u002Fclaude-code-plugins-plus-skills\u002Fadobe-incident-runbook\u002FSKILL.md",true,[],[84,96,106,115,121,128],{"skillNo":85,"name":86,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":92,"publishedAt":49},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[93,94,95],"model","model hierarchy","model hierarchy skill",{"skillNo":97,"name":98,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":102,"publishedAt":49},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[101],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},[103,104,105],"MCP","zoom","zoom mcp",{"skillNo":107,"name":108,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":49},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[112,113,114,104],"sdk","zoom apps sdk","apps",{"skillNo":116,"name":117,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":49},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[117],{"skillNo":122,"name":123,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":127,"publishedAt":49},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[126],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},[123],{"skillNo":129,"name":130,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":49},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[130]]