[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F7TK5F3JYS81Z37QTF5FJB":3,"skill-same:01M6F7TK5F3JYS81Z37QTF5FJB":70},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6F7TK5F3JYS81Z37QTF5FJB","lindy-incident-runbook",null,"Incident response runbook for Lindy AI integrations.\nUse when responding to incidents, troubleshooting outages,\nor creating on-call procedures.\nTrigger with phrases like \"lindy incident\", \"lindy outage\",\n\"lindy on-call\", \"lindy runbook\".","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\u002Flindy-pack\u002Fskills\u002Flindy-incident-runbook\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"runbook","lindy incident runbook","incident","when","incident response","for","incidents","with","trigger","io","call","use","edit","write","read","curl","integrations","troubleshooting","Bash","2026-11-10 10:12:30",false,"---\nname: lindy-incident-runbook\ndescription: |\n  Incident response runbook for Lindy AI integrations.\n  Use when responding to incidents, troubleshooting outages,\n  or creating on-call procedures.\n  Trigger with phrases like \"lindy incident\", \"lindy outage\",\n  \"lindy on-call\", \"lindy runbook\".\nallowed-tools: Read, Write, Edit, Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\n---\n\n# Lindy Incident Runbook\n\n## Overview\nIncident response procedures for Lindy AI integration issues.\n\n## Prerequisites\n- Access to Lindy dashboard\n- Monitoring dashboards available\n- Escalation contacts known\n- Admin access to production\n\n## Incident Severity Levels\n\n| Severity | Description | Response Time | Examples |\n|----------|-------------|---------------|----------|\n| SEV1 | Complete outage | 15 minutes | All agents failing |\n| SEV2 | Partial outage | 30 minutes | One critical agent down |\n| SEV3 | Degraded | 2 hours | High latency, some errors |\n| SEV4 | Minor | 24 hours | Cosmetic issues |\n\n## Quick Diagnostics\n\n### Step 1: Check Lindy Status\n```bash\n# Check Lindy status page\ncurl -s https:\u002F\u002Fstatus.lindy.ai\u002Fapi\u002Fv1\u002Fstatus | jq '.status'\n\n# Check API health\ncurl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  -H \"Authorization: Bearer $LINDY_API_KEY\" \\\n  https:\u002F\u002Fapi.lindy.ai\u002Fv1\u002Fhealth\n```\n\n### Step 2: Verify Authentication\n```bash\n# Test API key\ncurl -s -H \"Authorization: Bearer $LINDY_API_KEY\" \\\n  https:\u002F\u002Fapi.lindy.ai\u002Fv1\u002Fusers\u002Fme | jq '.email'\n```\n\n### Step 3: Check Rate Limits\n```bash\n# Check rate limit headers\ncurl -sI -H \"Authorization: Bearer $LINDY_API_KEY\" \\\n  https:\u002F\u002Fapi.lindy.ai\u002Fv1\u002Fusers\u002Fme | grep -i \"x-ratelimit\"\n```\n\n## Common Incidents\n\n### Incident: Complete API Outage\n\n**Symptoms:**\n- All API calls failing\n- 5xx errors from Lindy\n\n**Runbook:**\n```markdown\n1. [ ] Check https:\u002F\u002Fstatus.lindy.ai\n2. [ ] Verify it's not a local network issue\n3. [ ] Check if other services on same network work\n4. [ ] Enable fallback mode if available\n5. [ ] Notify stakeholders\n6. [ ] Open support ticket with Lindy\n7. [ ] Monitor status page for updates\n```\n\n**Fallback Code:**\n```typescript\nasync function runWithFallback(agentId: string, input: string) {\n  try {\n    return await lindy.agents.run(agentId, { input });\n  } catch (error: any) {\n    if (error.status >= 500) {\n      \u002F\u002F Enable fallback mode\n      return {\n        output: 'Service temporarily unavailable. Please try again later.',\n        fallback: true,\n      };\n    }\n    throw error;\n  }\n}\n```\n\n### Incident: Rate Limiting\n\n**Symptoms:**\n- 429 errors\n- \"Rate limit exceeded\" messages\n\n**Runbook:**\n```markdown\n1. [ ] Check current usage in dashboard\n2. [ ] Identify spike source (which agent\u002Fautomation)\n3. [ ] Reduce request rate or implement throttling\n4. [ ] Consider upgrading plan if legitimate traffic\n5. [ ] Implement request queuing\n```\n\n**Throttling Code:**\n```typescript\nconst queue = new PQueue({ concurrency: 5, interval: 1000, intervalCap: 10 });\n\nasync function throttledRun(agentId: string, input: string) {\n  return queue.add(() => lindy.agents.run(agentId, { input }));\n}\n```\n\n### Incident: Agent Failures\n\n**Symptoms:**\n- Specific agent not responding\n- Unexpected outputs\n- Timeout errors\n\n**Runbook:**\n```markdown\n1. [ ] Identify affected agent(s)\n2. [ ] Check agent configuration hasn't changed\n3. [ ] Review recent runs for patterns\n4. [ ] Test with simple input\n5. [ ] Check if tools are working\n6. [ ] Rollback to previous version if needed\n```\n\n**Diagnostic Script:**\n```typescript\nasync function diagnoseAgent(agentId: string) {\n  const lindy = new Lindy({ apiKey: process.env.LINDY_API_KEY });\n\n  \u002F\u002F Get agent details\n  const agent = await lindy.agents.get(agentId);\n  console.log('Agent:', agent.name, agent.status);\n\n  \u002F\u002F Check recent runs\n  const runs = await lindy.runs.list({ agentId, limit: 10 });\n  const failures = runs.filter((r: any) => r.status === 'failed');\n  console.log(`Failures: ${failures.length}\u002F${runs.length}`);\n\n  \u002F\u002F Test run\n  try {\n    const test = await lindy.agents.run(agentId, { input: 'Hello' });\n    console.log('Test run: SUCCESS');\n  } catch (e: any) {\n    console.log('Test run: FAILED -', e.message);\n  }\n\n  return { agent, runs, failures };\n}\n```\n\n### Incident: High Latency\n\n**Symptoms:**\n- Response times > 10 seconds\n- Timeouts increasing\n\n**Runbook:**\n```markdown\n1. [ ] Check Lindy status page for degradation\n2. [ ] Review latency metrics by agent\n3. [ ] Check if issue is with specific agent\n4. [ ] Verify instructions aren't causing long responses\n5. [ ] Consider reducing max_tokens\n6. [ ] Implement streaming if not already\n```\n\n## Escalation Matrix\n\n| Level | Contact | When |\n|-------|---------|------|\n| L1 | On-call engineer | Initial response |\n| L2 | Engineering lead | After 30 min SEV1\u002F2 |\n| L3 | VP Engineering | After 1 hour SEV1 |\n| Lindy | support@lindy.ai | External issue confirmed |\n\n## Post-Incident\n\n### Incident Report Template\n```markdown\n## Incident Report: [Title]\n\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** SEV1\u002F2\u002F3\u002F4\n**Impact:** [Description of user impact]\n\n### Timeline\n- HH:MM - Incident detected\n- HH:MM - On-call paged\n- HH:MM - Root cause identified\n- HH:MM - Resolution applied\n- HH:MM - All clear\n\n### Root Cause\n[What caused the incident]\n\n### Resolution\n[What fixed it]\n\n### Action Items\n- [ ] [Preventive action 1]\n- [ ] [Preventive action 2]\n```\n\n## Output\n- Quick diagnostic commands\n- Common incident runbooks\n- Fallback code patterns\n- Escalation procedures\n- Post-incident template\n\n## Resources\n- [Lindy Status](https:\u002F\u002Fstatus.lindy.ai)\n- [Lindy Support](https:\u002F\u002Fsupport.lindy.ai)\n- [API Reference](https:\u002F\u002Fdocs.lindy.ai\u002Fapi)\n\n## Next Steps\nProceed to `lindy-data-handling` for data management.\n","# Lindy Incident Runbook\n\n## Overview\nIncident response procedures for Lindy AI integration issues.\n\n## Prerequisites\n- Access to Lindy dashboard\n- Monitoring dashboards available\n- Escalation contacts known\n- Admin access to production\n\n## Incident Severity Levels\n\n| Severity | Description | Response Time | Examples |\n|----------|-------------|---------------|----------|\n| SEV1 | Complete outage | 15 minutes | All agents failing |\n| SEV2 | Partial outage | 30 minutes | One critical agent down |\n| SEV3 | Degraded | 2 hours | High latency, some errors |\n| SEV4 | Minor | 24 hours | Cosmetic issues |\n\n## Quick Diagnostics\n\n### Step 1: Check Lindy Status\n```bash\n# Check Lindy status page\ncurl -s https:\u002F\u002Fstatus.lindy.ai\u002Fapi\u002Fv1\u002Fstatus | jq '.status'\n\n# Check API health\ncurl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  -H \"Authorization: Bearer $LINDY_API_KEY\" \\\n  https:\u002F\u002Fapi.lindy.ai\u002Fv1\u002Fhealth\n```\n\n### Step 2: Verify Authentication\n```bash\n# Test API key\ncurl -s -H \"Authorization: Bearer $LINDY_API_KEY\" \\\n  https:\u002F\u002Fapi.lindy.ai\u002Fv1\u002Fusers\u002Fme | jq '.email'\n```\n\n### Step 3: Check Rate Limits\n```bash\n# Check rate limit headers\ncurl -sI -H \"Authorization: Bearer $LINDY_API_KEY\" \\\n  https:\u002F\u002Fapi.lindy.ai\u002Fv1\u002Fusers\u002Fme | grep -i \"x-ratelimit\"\n```\n\n## Common Incidents\n\n### Incident: Complete API Outage\n\n**Symptoms:**\n- All API calls failing\n- 5xx errors from Lindy\n\n**Runbook:**\n```markdown\n1. [ ] Check https:\u002F\u002Fstatus.lindy.ai\n2. [ ] Verify it's not a local network issue\n3. [ ] Check if other services on same network work\n4. [ ] Enable fallback mode if available\n5. [ ] Notify stakeholders\n6. [ ] Open support ticket with Lindy\n7. [ ] Monitor status page for updates\n```\n\n**Fallback Code:**\n```typescript\nasync function runWithFallback(agentId: string, input: string) {\n  try {\n    return await lindy.agents.run(agentId, { input });\n  } catch (error: any) {\n    if (error.status >= 500) {\n      \u002F\u002F Enable fallback mode\n      return {\n        output: 'Service temporarily unavailable. Please try again later.',\n        fallback: true,\n      };\n    }\n    throw error;\n  }\n}\n```\n\n### Incident: Rate Limiting\n\n**Symptoms:**\n- 429 errors\n- \"Rate limit exceeded\" messages\n\n**Runbook:**\n```markdown\n1. [ ] Check current usage in dashboard\n2. [ ] Identify spike source (which agent\u002Fautomation)\n3. [ ] Reduce request rate or implement throttling\n4. [ ] Consider upgrading plan if legitimate traffic\n5. [ ] Implement request queuing\n```\n\n**Throttling Code:**\n```typescript\nconst queue = new PQueue({ concurrency: 5, interval: 1000, intervalCap: 10 });\n\nasync function throttledRun(agentId: string, input: string) {\n  return queue.add(() => lindy.agents.run(agentId, { input }));\n}\n```\n\n### Incident: Agent Failures\n\n**Symptoms:**\n- Specific agent not responding\n- Unexpected outputs\n- Timeout errors\n\n**Runbook:**\n```markdown\n1. [ ] Identify affected agent(s)\n2. [ ] Check agent configuration hasn't changed\n3. [ ] Review recent runs for patterns\n4. [ ] Test with simple input\n5. [ ] Check if tools are working\n6. [ ] Rollback to previous version if needed\n```\n\n**Diagnostic Script:**\n```typescript\nasync function diagnoseAgent(agentId: string) {\n  const lindy = new Lindy({ apiKey: process.env.LINDY_API_KEY });\n\n  \u002F\u002F Get agent details\n  const agent = await lindy.agents.get(agentId);\n  console.log('Agent:', agent.name, agent.status);\n\n  \u002F\u002F Check recent runs\n  const runs = await lindy.runs.list({ agentId, limit: 10 });\n  const failures = runs.filter((r: any) => r.status === 'failed');\n  console.log(`Failures: ${failures.length}\u002F${runs.length}`);\n\n  \u002F\u002F Test run\n  try {\n    const test = await lindy.agents.run(agentId, { input: 'Hello' });\n    console.log('Test run: SUCCESS');\n  } catch (e: any) {\n    console.log('Test run: FAILED -', e.message);\n  }\n\n  return { agent, runs, failures };\n}\n```\n\n### Incident: High Latency\n\n**Symptoms:**\n- Response times > 10 seconds\n- Timeouts increasing\n\n**Runbook:**\n```markdown\n1. [ ] Check Lindy status page for degradation\n2. [ ] Review latency metrics by agent\n3. [ ] Check if issue is with specific agent\n4. [ ] Verify instructions aren't causing long responses\n5. [ ] Consider reducing max_tokens\n6. [ ] Implement streaming if not already\n```\n\n## Escalation Matrix\n\n| Level | Contact | When |\n|-------|---------|------|\n| L1 | On-call engineer | Initial response |\n| L2 | Engineering lead | After 30 min SEV1\u002F2 |\n| L3 | VP Engineering | After 1 hour SEV1 |\n| Lindy | support@lindy.ai | External issue confirmed |\n\n## Post-Incident\n\n### Incident Report Template\n```markdown\n## Incident Report: [Title]\n\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** SEV1\u002F2\u002F3\u002F4\n**Impact:** [Description of user impact]\n\n### Timeline\n- HH:MM - Incident detected\n- HH:MM - On-call paged\n- HH:MM - Root cause identified\n- HH:MM - Resolution applied\n- HH:MM - All clear\n\n### Root Cause\n[What caused the incident]\n\n### Resolution\n[What fixed it]\n\n### Action Items\n- [ ] [Preventive action 1]\n- [ ] [Preventive action 2]\n```\n\n## Output\n- Quick diagnostic commands\n- Common incident runbooks\n- Fallback code patterns\n- Escalation procedures\n- Post-incident template\n\n## Resources\n- [Lindy Status](https:\u002F\u002Fstatus.lindy.ai)\n- [Lindy Support](https:\u002F\u002Fsupport.lindy.ai)\n- [API Reference](https:\u002F\u002Fdocs.lindy.ai\u002Fapi)\n\n## Next Steps\nProceed to `lindy-data-handling` for data management.\n",{"name":5,"author":43,"license":15,"version":44,"description":45,"allowed-tools":46},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Incident response runbook for Lindy AI integrations.\nUse when responding to incidents, troubleshooting outages,\nor creating on-call procedures.\nTrigger with phrases like \"lindy incident\", \"lindy outage\",\n\"lindy on-call\", \"lindy runbook\".\n","Read, Write, Edit, Bash(curl:*)","main","90b50ed0778745a80fd5bfb13b1843d45b9e82f7","tests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Flindy-pack\u002Fskills\u002Flindy-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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add Dicklesworthstone\u002Fpi_agent_rust --skill lindy-incident-runbook",{"tool":62,"command":63},"bunx","bunx skills add Dicklesworthstone\u002Fpi_agent_rust --skill lindy-incident-runbook",{"tool":65,"command":66},"pnpm","pnpm dlx skills add Dicklesworthstone\u002Fpi_agent_rust --skill lindy-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Flindy-pack\u002Fskills\u002Flindy-incident-runbook\u002FSKILL.md",true,[],[71,104,138,161,187,213],{"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":75,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":84,"publishedAt":103},"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",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,26,101,102],"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":114,"publishedAt":38},"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",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000009","前端开发",[115,116,91,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,30,96,132,133,134,135,24,136,137],"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":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":149,"publishedAt":38},"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",[145,148],{"categoryNo":146,"categoryName":147,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":112,"categoryName":113,"taxonomyType":82,"taxonomyTypeDesc":83},[150,151,152,119,153,154,116,155,89,156,129,157,158,159,160,26,24],"testing","webapp testing","webapp","screenshots","playwright","debugging","browser","logs","applications","behavior","local",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":38},"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",[],[169,170,171,172,173,174,175,176,30,177,178,179,180,181,182,183,26,184,185,186,24,22],"analysis","neuropixels analysis","spike","metrics","data","open","quality","user","recordings","Neural","motion","visual","quality metrics","unit","sorting","curation","recording","load",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":191,"sourceHtmlUrl":192,"categories":193,"keywords":197,"publishedAt":38},"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",[194],{"categoryNo":195,"categoryName":196,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000023","Skill与智能体开发",[198,199,200,201,202,203,204,205,35,206,207,208,209,210,26,24,211,22,212],"skill creator","creator","workflows","create","update","capabilities","knowledge","tool","specialized","guide","new skill","existing skill","users","Existing","new",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":217,"sourceHtmlUrl":218,"categories":219,"keywords":221,"publishedAt":38},"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",[220],{"categoryNo":195,"categoryName":196,"taxonomyType":82,"taxonomyTypeDesc":83},[215,222,223,224,225,226,227,156,228,229,30,230,231,232,233,24,234],"google","browser automation","gemini","automation","auth","code","library","management","only","document","query","Citation","source"]