[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F8KADX9GQVMCVT22784RZV":3,"skill-same:01M6F8KADX9GQVMCVT22784RZV":75},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6F8KADX9GQVMCVT22784RZV","perplexity-incident-runbook",null,"Execute Perplexity incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Perplexity-related outages, investigating errors,\nor running post-incident reviews for Perplexity integration failures.\nTrigger with phrases like \"perplexity incident\", \"perplexity outage\",\n\"perplexity down\", \"perplexity on-call\", \"perplexity emergency\", \"perplexity 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\u002Fperplexity-pack\u002Fskills\u002Fperplexity-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],"perplexity","runbook","perplexity incident runbook","incident","running","incident response","when","down","for","errors","reviews","with","post","trigger","io","call","use","read","broken","curl","postmortem","Bash","kubectl","integration","2026-11-10 10:12:30",false,"---\nname: perplexity-incident-runbook\ndescription: |\n  Execute Perplexity incident response procedures with triage, mitigation, and postmortem.\n  Use when responding to Perplexity-related outages, investigating errors,\n  or running post-incident reviews for Perplexity integration failures.\n  Trigger with phrases like \"perplexity incident\", \"perplexity outage\",\n  \"perplexity down\", \"perplexity on-call\", \"perplexity emergency\", \"perplexity broken\".\nallowed-tools: Read, Grep, Bash(kubectl:*), Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\n---\n\n# Perplexity Incident Runbook\n\n## Overview\nRapid incident response procedures for Perplexity-related outages.\n\n## Prerequisites\n- Access to Perplexity 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 | Perplexity 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\n# 1. Check Perplexity status\ncurl -s https:\u002F\u002Fstatus.perplexity.com | jq\n\n# 2. Check our integration health\ncurl -s https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.perplexity'\n\n# 3. Check error rate (last 5 min)\ncurl -s localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(perplexity_errors_total[5m])\n\n# 4. Recent error logs\nkubectl logs -l app=perplexity-integration --since=5m | grep -i error | tail -20\n```\n\n## Decision Tree\n\n```\nPerplexity API returning errors?\n├─ YES: Is status.perplexity.com showing incident?\n│   ├─ YES → Wait for Perplexity 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\n# Verify API key is set\nkubectl get secret perplexity-secrets -o jsonpath='{.data.api-key}' | base64 -d\n\n# Check if key was rotated\n# → Verify in Perplexity dashboard\n\n# Remediation: Update secret and restart pods\nkubectl create secret generic perplexity-secrets --from-literal=api-key=NEW_KEY --dry-run=client -o yaml | kubectl apply -f -\nkubectl rollout restart deployment\u002Fperplexity-integration\n```\n\n### 429 - Rate Limited\n```bash\n# Check rate limit headers\ncurl -v https:\u002F\u002Fapi.perplexity.com 2>&1 | grep -i rate\n\n# Enable request queuing\nkubectl set env deployment\u002Fperplexity-integration RATE_LIMIT_MODE=queue\n\n# Long-term: Contact Perplexity for limit increase\n```\n\n### 500\u002F503 - Perplexity Errors\n```bash\n# Enable graceful degradation\nkubectl set env deployment\u002Fperplexity-integration PERPLEXITY_FALLBACK=true\n\n# Notify users of degraded service\n# Update status page\n\n# Monitor Perplexity status for resolution\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\n? P1 INCIDENT: Perplexity 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```\nPerplexity Integration Issue\n\nWe're experiencing issues with our Perplexity 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\n# Generate debug bundle\n.\u002Fscripts\u002Fperplexity-debug-bundle.sh\n\n# Export relevant logs\nkubectl logs -l app=perplexity-integration --since=1h > incident-logs.txt\n\n# Capture metrics\ncurl \"localhost:9090\u002Fapi\u002Fv1\u002Fquery_range?query=perplexity_errors_total&start=2h\" > metrics.json\n```\n\n### Postmortem Template\n```markdown\n## Incident: Perplexity [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 Perplexity-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\ncurl -sf https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.perplexity.status' || echo \"UNHEALTHY\"\n```\n\n## Resources\n- [Perplexity Status Page](https:\u002F\u002Fstatus.perplexity.com)\n- [Perplexity Support](https:\u002F\u002Fsupport.perplexity.com)\n\n## Next Steps\nFor data handling, see `perplexity-data-handling`.","# Perplexity Incident Runbook\n\n## Overview\nRapid incident response procedures for Perplexity-related outages.\n\n## Prerequisites\n- Access to Perplexity 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 | Perplexity 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\n# 1. Check Perplexity status\ncurl -s https:\u002F\u002Fstatus.perplexity.com | jq\n\n# 2. Check our integration health\ncurl -s https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.perplexity'\n\n# 3. Check error rate (last 5 min)\ncurl -s localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(perplexity_errors_total[5m])\n\n# 4. Recent error logs\nkubectl logs -l app=perplexity-integration --since=5m | grep -i error | tail -20\n```\n\n## Decision Tree\n\n```\nPerplexity API returning errors?\n├─ YES: Is status.perplexity.com showing incident?\n│   ├─ YES → Wait for Perplexity 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\n# Verify API key is set\nkubectl get secret perplexity-secrets -o jsonpath='{.data.api-key}' | base64 -d\n\n# Check if key was rotated\n# → Verify in Perplexity dashboard\n\n# Remediation: Update secret and restart pods\nkubectl create secret generic perplexity-secrets --from-literal=api-key=NEW_KEY --dry-run=client -o yaml | kubectl apply -f -\nkubectl rollout restart deployment\u002Fperplexity-integration\n```\n\n### 429 - Rate Limited\n```bash\n# Check rate limit headers\ncurl -v https:\u002F\u002Fapi.perplexity.com 2>&1 | grep -i rate\n\n# Enable request queuing\nkubectl set env deployment\u002Fperplexity-integration RATE_LIMIT_MODE=queue\n\n# Long-term: Contact Perplexity for limit increase\n```\n\n### 500\u002F503 - Perplexity Errors\n```bash\n# Enable graceful degradation\nkubectl set env deployment\u002Fperplexity-integration PERPLEXITY_FALLBACK=true\n\n# Notify users of degraded service\n# Update status page\n\n# Monitor Perplexity status for resolution\n```\n\n## Communication Templates\n\n### Internal (Slack)\n```\n? P1 INCIDENT: Perplexity 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```\nPerplexity Integration Issue\n\nWe're experiencing issues with our Perplexity 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\n# Generate debug bundle\n.\u002Fscripts\u002Fperplexity-debug-bundle.sh\n\n# Export relevant logs\nkubectl logs -l app=perplexity-integration --since=1h > incident-logs.txt\n\n# Capture metrics\ncurl \"localhost:9090\u002Fapi\u002Fv1\u002Fquery_range?query=perplexity_errors_total&start=2h\" > metrics.json\n```\n\n### Postmortem Template\n```markdown\n## Incident: Perplexity [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 Perplexity-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\ncurl -sf https:\u002F\u002Fapi.yourapp.com\u002Fhealth | jq '.services.perplexity.status' || echo \"UNHEALTHY\"\n```\n\n## Resources\n- [Perplexity Status Page](https:\u002F\u002Fstatus.perplexity.com)\n- [Perplexity Support](https:\u002F\u002Fsupport.perplexity.com)\n\n## Next Steps\nFor data handling, see `perplexity-data-handling`.",{"name":5,"author":48,"license":15,"version":49,"description":50,"allowed-tools":51},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Perplexity incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Perplexity-related outages, investigating errors,\nor running post-incident reviews for Perplexity integration failures.\nTrigger with phrases like \"perplexity incident\", \"perplexity outage\",\n\"perplexity down\", \"perplexity on-call\", \"perplexity emergency\", \"perplexity broken\".\n","Read, Grep, Bash(kubectl:*), Bash(curl:*)","main","90b50ed0778745a80fd5bfb13b1843d45b9e82f7","tests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fperplexity-pack\u002Fskills\u002Fperplexity-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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Dicklesworthstone\u002Fpi_agent_rust --skill perplexity-incident-runbook",{"tool":67,"command":68},"bunx","bunx skills add Dicklesworthstone\u002Fpi_agent_rust --skill perplexity-incident-runbook",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Dicklesworthstone\u002Fpi_agent_rust --skill perplexity-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fperplexity-pack\u002Fskills\u002Fperplexity-incident-runbook\u002FSKILL.md",true,[],[76,115,139,165,192,214],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":89,"publishedAt":43},"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.","Apache-2.0","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",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,35,108,109,110,111,112,27,113,114],"web artifacts builder","web","artifacts","artifacts builder","builder","frontend","css","components","react","component","routing","state management","state","shadcn","file","ui","Tools","Tailwind","html","single-file","simple","ui components","multi","jsx","suite",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":126,"publishedAt":43},"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",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},[127,128,129,95,130,131,91,132,133,134,105,135,136,137,138,30,27],"testing","webapp testing","webapp","screenshots","playwright","debugging","toolkit","browser","logs","applications","behavior","local",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":43},"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",[],[147,148,149,150,151,152,153,154,35,155,156,157,158,159,160,161,30,162,163,164,27,25],"analysis","neuropixels analysis","spike","metrics","data","open","quality","user","recordings","Neural","motion","visual","quality metrics","unit","sorting","curation","recording","load",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":169,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":43},"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",[172],{"categoryNo":173,"categoryName":174,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发",[176,177,178,179,180,181,182,183,184,185,186,187,188,189,30,27,190,25,191],"skill creator","creator","workflows","create","update","capabilities","knowledge","tool","integrations","specialized","guide","new skill","existing skill","users","Existing","new",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":196,"sourceHtmlUrl":197,"categories":198,"keywords":200,"publishedAt":43},"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",[199],{"categoryNo":173,"categoryName":174,"taxonomyType":87,"taxonomyTypeDesc":88},[194,201,202,203,204,205,206,134,207,208,35,209,210,211,212,27,213],"google","browser automation","gemini","automation","auth","code","library","management","only","document","query","Citation","source",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":218,"sourceHtmlUrl":219,"categories":220,"keywords":227,"publishedAt":43},"01M6FDHPXE10J3XGTCH5HBHS1M","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fslack-gif-creator\u002FSKILL.md",[221,224],{"categoryNo":222,"categoryName":223,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":225,"categoryName":226,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000016","图像与多媒体",[228,229,230,177,231,106,232,233,182,35,234,189,235,236,237,27,238,25],"slack gif creator","slack","gif","validation","constraints","Animation","me","make","Utilities","concepts","request"]