[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F80FV9ZJPE21K7HDRXWZMD":3,"skill-same:01M6F80FV9ZJPE21K7HDRXWZMD":76},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6F80FV9ZJPE21K7HDRXWZMD","lokalise-incident-runbook",null,"Execute Lokalise incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Lokalise-related outages, investigating errors,\nor running post-incident reviews for Lokalise integration failures.\nTrigger with phrases like \"lokalise incident\", \"lokalise outage\",\n\"lokalise down\", \"lokalise on-call\", \"lokalise emergency\", \"translations broken\".","Dicklesworthstone\u002Fpi_agent_rust","Dicklesworthstone","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F35050222?v=4","01M6CG26AR942CSVMN1M5E3DSE","Jeff Emanuel","01M6CG26EPP71PSHW1VDS71121",1992,"MIT","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Flokalise-pack\u002Fskills\u002Flokalise-incident-runbook\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"runbook","lokalise incident runbook","incident","call","running","when","down","for","errors","reviews","with","post","trigger","io","incident response","use","read","broken","curl","grep","postmortem","Bash","post-incident","integration","triage","2026-11-10 10:12:30",false,"---\nname: lokalise-incident-runbook\ndescription: |\n  Execute Lokalise incident response procedures with triage, mitigation, and postmortem.\n  Use when responding to Lokalise-related outages, investigating errors,\n  or running post-incident reviews for Lokalise integration failures.\n  Trigger with phrases like \"lokalise incident\", \"lokalise outage\",\n  \"lokalise down\", \"lokalise on-call\", \"lokalise emergency\", \"translations broken\".\nallowed-tools: Read, Grep, Bash(curl:*), Bash(lokalise2:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\n---\n\n# Lokalise Incident Runbook\n\n## Overview\nRapid incident response procedures for Lokalise-related outages and issues.\n\n## Prerequisites\n- Access to Lokalise dashboard and status page\n- Application logs and monitoring dashboards\n- Communication channels (Slack, PagerDuty)\n- Rollback procedures documented\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Complete outage | \u003C 15 min | Lokalise API unreachable, all translations missing |\n| P2 | Degraded service | \u003C 1 hour | High latency, partial failures, key languages affected |\n| P3 | Minor impact | \u003C 4 hours | Webhook delays, non-critical translations missing |\n| P4 | No user impact | Next business day | Monitoring gaps, sync delays |\n\n## Quick Triage Commands\n\n```bash\n# 1. Check Lokalise API status\ncurl -s https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fsystem\u002Fhealth | jq\n\n# 2. Check Lokalise status page\ncurl -s https:\u002F\u002Fstatus.lokalise.com\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status.description'\n\n# 3. Test API authentication\ncurl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  -H \"X-Api-Token: $LOKALISE_API_TOKEN\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects?limit=1\"\n\n# 4. Check your app's translation health\ncurl -s https:\u002F\u002Fyour-app.com\u002Fhealth\u002Flokalise | jq\n\n# 5. Check recent error logs (last 5 min)\ngrep -i \"lokalise\" \u002Fvar\u002Flog\u002Fapp\u002F*.log | tail -50\n```\n\n## Decision Tree\n\n```\nTranslations missing\u002Fbroken?\n├─ YES: Is https:\u002F\u002Fstatus.lokalise.com showing incident?\n│   ├─ YES → Enable fallback translations. Monitor status page.\n│   └─ NO → Check our integration. Continue triage below.\n└─ NO: Is sync failing?\n    ├─ YES → Check CI\u002FCD pipeline, API token validity\n    └─ NO → Likely localized issue. Check specific component.\n\nAPI returning errors?\n├─ 401 → Token expired\u002Finvalid. Rotate token.\n├─ 403 → Permission denied. Check project access.\n├─ 404 → Project\u002Fkey not found. Verify IDs.\n├─ 429 → Rate limited. Enable backoff\u002Fqueuing.\n└─ 5xx → Lokalise issue. Enable fallback, monitor status.\n```\n\n## Immediate Actions by Error Type\n\n### 401\u002F403 - Authentication\u002FAuthorization\n```bash\n# Verify token is set\necho \"Token set: ${LOKALISE_API_TOKEN:+YES}\"\n\n# Test token validity\ncurl -s -H \"X-Api-Token: $LOKALISE_API_TOKEN\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects?limit=1\" | jq '.projects[0].name \u002F\u002F .error'\n\n# If token is invalid:\n# 1. Generate new token in Lokalise Profile Settings\n# 2. Update in secret manager\n# 3. Restart affected services\n```\n\n### 429 - Rate Limited\n```bash\n# Check current rate limit status\ncurl -s -I -H \"X-Api-Token: $LOKALISE_API_TOKEN\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\" | grep -i \"x-ratelimit\"\n\n# Immediate mitigation:\n# 1. Reduce concurrent requests\n# 2. Add delays between API calls\n# 3. Enable request queuing\n\n# Application config\nexport LOKALISE_RATE_LIMIT_MODE=queue\nexport LOKALISE_REQUEST_DELAY_MS=200\n```\n\n### 5xx - Lokalise Server Errors\n```bash\n# Check Lokalise status\ncurl -s https:\u002F\u002Fstatus.lokalise.com\u002Fapi\u002Fv2\u002Fstatus.json | jq\n\n# Enable graceful degradation\nexport LOKALISE_FALLBACK_ENABLED=true\n\n# Use bundled translations as fallback\n# Your app should fall back to static locale files\n\n# Monitor for resolution\nwatch -n 60 'curl -s https:\u002F\u002Fstatus.lokalise.com\u002Fapi\u002Fv2\u002Fstatus.json | jq \".status.description\"'\n```\n\n### Missing Translations\n```bash\n# Check if translations exist in Lokalise\nlokalise2 --token \"$LOKALISE_API_TOKEN\" \\\n  --project-id \"$LOKALISE_PROJECT_ID\" \\\n  key list --filter-untranslated-any 1 | head -20\n\n# Check local translation files\nls -la src\u002Flocales\u002F\ncat src\u002Flocales\u002Fen.json | jq 'keys | length'\n\n# If files missing, re-download\nnpm run i18n:pull\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\n:red_circle: P1 INCIDENT: Lokalise Integration\nStatus: INVESTIGATING\nImpact: [Translations not loading for all users]\nCurrent action: [Checking API status and enabling fallback]\nNext update: [Time + 15 min]\nIncident commander: @[name]\n```\n\n### External (Status Page)\n```\nTranslation Service Issue\n\nWe're experiencing issues with our translation service.\nSome users may see English text instead of their preferred language.\n\nWe're actively investigating and will provide updates.\n\nLast updated: [timestamp]\n```\n\n## Post-Incident\n\n### Evidence Collection\n```bash\n# Generate debug bundle\nbash scripts\u002Flokalise-debug-bundle.sh\n\n# Export relevant logs\ngrep -i \"lokalise\" \u002Fvar\u002Flog\u002Fapp\u002F*.log > incident-logs.txt\n\n# Export metrics snapshot\ncurl \"http:\u002F\u002Fprometheus:9090\u002Fapi\u002Fv1\u002Fquery_range?query=lokalise_errors_total&start=-2h\" > metrics.json\n\n# Screenshot dashboards\n# Document timeline in incident channel\n```\n\n### Postmortem Template\n```markdown\n## Incident: Lokalise [Error Type]\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n**Incident Commander:** [Name]\n\n### Summary\n[1-2 sentence description of what happened]\n\n### Timeline (all times UTC)\n- HH:MM - [Alert triggered \u002F Issue reported]\n- HH:MM - [Investigation started]\n- HH:MM - [Root cause identified]\n- HH:MM - [Mitigation applied]\n- HH:MM - [Service restored]\n\n### Root Cause\n[Technical explanation of what went wrong]\n\n### Impact\n- Users affected: [N]\n- Duration of user impact: [X minutes]\n- Translations affected: [Languages\u002Fkeys]\n\n### What Went Well\n- [Positive aspects of response]\n\n### What Could Be Improved\n- [Areas for improvement]\n\n### Action Items\n- [ ] [Preventive measure] - Owner - Due date\n- [ ] [Documentation update] - Owner - Due date\n- [ ] [Monitoring improvement] - Owner - Due date\n```\n\n## Rollback Procedures\n\n### Revert to Bundled Translations\n```bash\n# If translations are corrupted, revert to last known good\ngit checkout HEAD~1 -- src\u002Flocales\u002F\n\n# Rebuild and deploy\nnpm run build\nnpm run deploy\n\n# Disable auto-sync temporarily\nexport LOKALISE_AUTO_SYNC=false\n```\n\n### Re-download from Lokalise\n```bash\n# Download reviewed translations only\nlokalise2 --token \"$LOKALISE_API_TOKEN\" \\\n  --project-id \"$LOKALISE_PROJECT_ID\" \\\n  file download \\\n  --format json \\\n  --filter-data reviewed \\\n  --unzip-to .\u002Fsrc\u002Flocales\n```\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| Logs unavailable | Logging down | Check logging service |\n| Fallback not working | Not configured | Enable static fallback |\n| Token rotation fails | Permission denied | Escalate to admin |\n\n## Examples\n\n### One-Line Health Check\n```bash\ncurl -sf https:\u002F\u002Fyour-app.com\u002Fhealth\u002Flokalise | jq '.status' || echo \"UNHEALTHY\"\n```\n\n### Quick Fallback Enable\n```typescript\n\u002F\u002F Emergency fallback - use in incident\nprocess.env.LOKALISE_FALLBACK_ENABLED = \"true\";\n\n\u002F\u002F Your translation loader should check this\nconst useFallback = process.env.LOKALISE_FALLBACK_ENABLED === \"true\";\nif (useFallback) {\n  return loadBundledTranslations(locale);\n}\n```\n\n## Resources\n- [Lokalise Status Page](https:\u002F\u002Fstatus.lokalise.com)\n- [Lokalise Support](mailto:support@lokalise.com)\n- [Community Forum](https:\u002F\u002Fcommunity.lokalise.com)\n\n## Next Steps\nFor data handling, see `lokalise-data-handling`.\n","# Lokalise Incident Runbook\n\n## Overview\nRapid incident response procedures for Lokalise-related outages and issues.\n\n## Prerequisites\n- Access to Lokalise dashboard and status page\n- Application logs and monitoring dashboards\n- Communication channels (Slack, PagerDuty)\n- Rollback procedures documented\n\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Complete outage | \u003C 15 min | Lokalise API unreachable, all translations missing |\n| P2 | Degraded service | \u003C 1 hour | High latency, partial failures, key languages affected |\n| P3 | Minor impact | \u003C 4 hours | Webhook delays, non-critical translations missing |\n| P4 | No user impact | Next business day | Monitoring gaps, sync delays |\n\n## Quick Triage Commands\n\n```bash\n# 1. Check Lokalise API status\ncurl -s https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fsystem\u002Fhealth | jq\n\n# 2. Check Lokalise status page\ncurl -s https:\u002F\u002Fstatus.lokalise.com\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status.description'\n\n# 3. Test API authentication\ncurl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  -H \"X-Api-Token: $LOKALISE_API_TOKEN\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects?limit=1\"\n\n# 4. Check your app's translation health\ncurl -s https:\u002F\u002Fyour-app.com\u002Fhealth\u002Flokalise | jq\n\n# 5. Check recent error logs (last 5 min)\ngrep -i \"lokalise\" \u002Fvar\u002Flog\u002Fapp\u002F*.log | tail -50\n```\n\n## Decision Tree\n\n```\nTranslations missing\u002Fbroken?\n├─ YES: Is https:\u002F\u002Fstatus.lokalise.com showing incident?\n│   ├─ YES → Enable fallback translations. Monitor status page.\n│   └─ NO → Check our integration. Continue triage below.\n└─ NO: Is sync failing?\n    ├─ YES → Check CI\u002FCD pipeline, API token validity\n    └─ NO → Likely localized issue. Check specific component.\n\nAPI returning errors?\n├─ 401 → Token expired\u002Finvalid. Rotate token.\n├─ 403 → Permission denied. Check project access.\n├─ 404 → Project\u002Fkey not found. Verify IDs.\n├─ 429 → Rate limited. Enable backoff\u002Fqueuing.\n└─ 5xx → Lokalise issue. Enable fallback, monitor status.\n```\n\n## Immediate Actions by Error Type\n\n### 401\u002F403 - Authentication\u002FAuthorization\n```bash\n# Verify token is set\necho \"Token set: ${LOKALISE_API_TOKEN:+YES}\"\n\n# Test token validity\ncurl -s -H \"X-Api-Token: $LOKALISE_API_TOKEN\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects?limit=1\" | jq '.projects[0].name \u002F\u002F .error'\n\n# If token is invalid:\n# 1. Generate new token in Lokalise Profile Settings\n# 2. Update in secret manager\n# 3. Restart affected services\n```\n\n### 429 - Rate Limited\n```bash\n# Check current rate limit status\ncurl -s -I -H \"X-Api-Token: $LOKALISE_API_TOKEN\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\" | grep -i \"x-ratelimit\"\n\n# Immediate mitigation:\n# 1. Reduce concurrent requests\n# 2. Add delays between API calls\n# 3. Enable request queuing\n\n# Application config\nexport LOKALISE_RATE_LIMIT_MODE=queue\nexport LOKALISE_REQUEST_DELAY_MS=200\n```\n\n### 5xx - Lokalise Server Errors\n```bash\n# Check Lokalise status\ncurl -s https:\u002F\u002Fstatus.lokalise.com\u002Fapi\u002Fv2\u002Fstatus.json | jq\n\n# Enable graceful degradation\nexport LOKALISE_FALLBACK_ENABLED=true\n\n# Use bundled translations as fallback\n# Your app should fall back to static locale files\n\n# Monitor for resolution\nwatch -n 60 'curl -s https:\u002F\u002Fstatus.lokalise.com\u002Fapi\u002Fv2\u002Fstatus.json | jq \".status.description\"'\n```\n\n### Missing Translations\n```bash\n# Check if translations exist in Lokalise\nlokalise2 --token \"$LOKALISE_API_TOKEN\" \\\n  --project-id \"$LOKALISE_PROJECT_ID\" \\\n  key list --filter-untranslated-any 1 | head -20\n\n# Check local translation files\nls -la src\u002Flocales\u002F\ncat src\u002Flocales\u002Fen.json | jq 'keys | length'\n\n# If files missing, re-download\nnpm run i18n:pull\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\n:red_circle: P1 INCIDENT: Lokalise Integration\nStatus: INVESTIGATING\nImpact: [Translations not loading for all users]\nCurrent action: [Checking API status and enabling fallback]\nNext update: [Time + 15 min]\nIncident commander: @[name]\n```\n\n### External (Status Page)\n```\nTranslation Service Issue\n\nWe're experiencing issues with our translation service.\nSome users may see English text instead of their preferred language.\n\nWe're actively investigating and will provide updates.\n\nLast updated: [timestamp]\n```\n\n## Post-Incident\n\n### Evidence Collection\n```bash\n# Generate debug bundle\nbash scripts\u002Flokalise-debug-bundle.sh\n\n# Export relevant logs\ngrep -i \"lokalise\" \u002Fvar\u002Flog\u002Fapp\u002F*.log > incident-logs.txt\n\n# Export metrics snapshot\ncurl \"http:\u002F\u002Fprometheus:9090\u002Fapi\u002Fv1\u002Fquery_range?query=lokalise_errors_total&start=-2h\" > metrics.json\n\n# Screenshot dashboards\n# Document timeline in incident channel\n```\n\n### Postmortem Template\n```markdown\n## Incident: Lokalise [Error Type]\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n**Incident Commander:** [Name]\n\n### Summary\n[1-2 sentence description of what happened]\n\n### Timeline (all times UTC)\n- HH:MM - [Alert triggered \u002F Issue reported]\n- HH:MM - [Investigation started]\n- HH:MM - [Root cause identified]\n- HH:MM - [Mitigation applied]\n- HH:MM - [Service restored]\n\n### Root Cause\n[Technical explanation of what went wrong]\n\n### Impact\n- Users affected: [N]\n- Duration of user impact: [X minutes]\n- Translations affected: [Languages\u002Fkeys]\n\n### What Went Well\n- [Positive aspects of response]\n\n### What Could Be Improved\n- [Areas for improvement]\n\n### Action Items\n- [ ] [Preventive measure] - Owner - Due date\n- [ ] [Documentation update] - Owner - Due date\n- [ ] [Monitoring improvement] - Owner - Due date\n```\n\n## Rollback Procedures\n\n### Revert to Bundled Translations\n```bash\n# If translations are corrupted, revert to last known good\ngit checkout HEAD~1 -- src\u002Flocales\u002F\n\n# Rebuild and deploy\nnpm run build\nnpm run deploy\n\n# Disable auto-sync temporarily\nexport LOKALISE_AUTO_SYNC=false\n```\n\n### Re-download from Lokalise\n```bash\n# Download reviewed translations only\nlokalise2 --token \"$LOKALISE_API_TOKEN\" \\\n  --project-id \"$LOKALISE_PROJECT_ID\" \\\n  file download \\\n  --format json \\\n  --filter-data reviewed \\\n  --unzip-to .\u002Fsrc\u002Flocales\n```\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| Logs unavailable | Logging down | Check logging service |\n| Fallback not working | Not configured | Enable static fallback |\n| Token rotation fails | Permission denied | Escalate to admin |\n\n## Examples\n\n### One-Line Health Check\n```bash\ncurl -sf https:\u002F\u002Fyour-app.com\u002Fhealth\u002Flokalise | jq '.status' || echo \"UNHEALTHY\"\n```\n\n### Quick Fallback Enable\n```typescript\n\u002F\u002F Emergency fallback - use in incident\nprocess.env.LOKALISE_FALLBACK_ENABLED = \"true\";\n\n\u002F\u002F Your translation loader should check this\nconst useFallback = process.env.LOKALISE_FALLBACK_ENABLED === \"true\";\nif (useFallback) {\n  return loadBundledTranslations(locale);\n}\n```\n\n## Resources\n- [Lokalise Status Page](https:\u002F\u002Fstatus.lokalise.com)\n- [Lokalise Support](mailto:support@lokalise.com)\n- [Community Forum](https:\u002F\u002Fcommunity.lokalise.com)\n\n## Next Steps\nFor data handling, see `lokalise-data-handling`.\n",{"name":5,"author":49,"license":15,"version":50,"description":51,"allowed-tools":52},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Lokalise incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Lokalise-related outages, investigating errors,\nor running post-incident reviews for Lokalise integration failures.\nTrigger with phrases like \"lokalise incident\", \"lokalise outage\",\n\"lokalise down\", \"lokalise on-call\", \"lokalise emergency\", \"translations broken\".\n","Read, Grep, Bash(curl:*), Bash(lokalise2:*)","main","90b50ed0778745a80fd5bfb13b1843d45b9e82f7","tests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Flokalise-pack\u002Fskills\u002Flokalise-incident-runbook",233,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust","https:\u002F\u002Fgithub.com\u002FDicklesworthstone","https:\u002F\u002Fwww.jeffreyemanuel.com\u002F","Building in NY","2026-11-15 01:54:15",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add Dicklesworthstone\u002Fpi_agent_rust --skill lokalise-incident-runbook",{"tool":68,"command":69},"bunx","bunx skills add Dicklesworthstone\u002Fpi_agent_rust --skill lokalise-incident-runbook",{"tool":71,"command":72},"pnpm","pnpm dlx skills add Dicklesworthstone\u002Fpi_agent_rust --skill lokalise-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Flokalise-pack\u002Fskills\u002Flokalise-incident-runbook\u002FSKILL.md",true,[],[77,110,144,167,193,220],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":90,"publishedAt":109},"01M6FCR7G5A005P364Z6ZWCJDP","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Ftheme-factory\u002FSKILL.md",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,29,107,108],"theme factory","factory","theme","docs","toolkit","generate","artifacts","SET","fly","slides","landing","html","styling","artifact","pages","themes","you","fonts","2026-11-11 15:11:14",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":120,"publishedAt":44},"01M6FEGPPK0ZTKCCM0R3E3KS33","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000009","前端开发",[121,122,97,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,34,102,138,139,140,141,26,142,143],"web artifacts builder","web","artifacts builder","builder","frontend","css","components","react","component","routing","state management","state","shadcn","file","ui","Tools","Tailwind","single-file","simple","ui components","multi","jsx","suite",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":155,"publishedAt":44},"01M6FEE9VTK1W4GY21AKREJXRG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[151,154],{"categoryNo":152,"categoryName":153,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":118,"categoryName":119,"taxonomyType":88,"taxonomyTypeDesc":89},[156,157,158,125,159,160,122,161,95,162,135,163,164,165,166,29,26],"testing","webapp testing","webapp","screenshots","playwright","debugging","browser","logs","applications","behavior","local",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":44},"01M6FE20F7ZTQBFWKF4MPJ2SBX","neuropixels-analysis","Neuropixels neural recording analysis. Load SpikeGLX\u002FOpenEphys data, preprocess, motion correction, Kilosort4 spike sorting, quality metrics, Allen\u002FIBL curation, AI-assisted visual analysis, for Neuropixels 1.0\u002F2.0 extracellular electrophysiology. Use when working with neural recordings, spike sorting, extracellular electrophysiology, or when the user mentions Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, or unit curation.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fneuropixels-analysis\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fneuropixels-analysis\u002FSKILL.md",[],[175,176,177,178,179,180,181,182,34,183,184,185,186,187,188,189,29,190,191,192,26,24],"analysis","neuropixels analysis","spike","metrics","data","open","quality","user","recordings","Neural","motion","visual","quality metrics","unit","sorting","curation","recording","load",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":197,"sourceHtmlUrl":198,"categories":199,"keywords":203,"publishedAt":44},"01M6FDP0PDK6F1GGX395C7625Z","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FSKILL.md",[200],{"categoryNo":201,"categoryName":202,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000023","Skill与智能体开发",[204,205,206,207,208,209,210,211,212,213,214,215,216,217,29,26,218,24,219],"skill creator","creator","workflows","create","update","capabilities","knowledge","tool","integrations","specialized","guide","new skill","existing skill","users","Existing","new",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":224,"sourceHtmlUrl":225,"categories":226,"keywords":228,"publishedAt":44},"01M6FDM8Y7VK7NYG9SM7QPA3PW","notebooklm","Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotebooklm\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotebooklm\u002FSKILL.md",[227],{"categoryNo":201,"categoryName":202,"taxonomyType":88,"taxonomyTypeDesc":89},[222,229,230,231,232,233,234,162,235,236,34,237,238,239,240,26,241],"google","browser automation","gemini","automation","auth","code","library","management","only","document","query","Citation","source"]