[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F8985CGFVA5F9P6SWBHB5K":3,"skill-same:01M6F8985CGFVA5F9P6SWBHB5K":79},{"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":23,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6F8985CGFVA5F9P6SWBHB5K","obsidian-deploy-integration",null,"Publish Obsidian plugins to the community plugin directory.\nUse when releasing your first plugin, updating existing plugins,\nor managing the community plugin submission process.\nTrigger with phrases like \"publish obsidian plugin\", \"obsidian community plugins\",\n\"submit obsidian plugin\", \"obsidian plugin directory\".","Dicklesworthstone\u002Fpi_agent_rust","Dicklesworthstone","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F35050222?v=4","01M6CG26AR942CSVMN1M5E3DSE","Jeff Emanuel","01M6CG26EPP71PSHW1VDS71121",1979,"MIT","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fobsidian-pack\u002Fskills\u002Fobsidian-deploy-integration\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"obsidian","deploy","integration","obsidian deploy integration","when","directory","submission","Existing","with","submit","trigger","io","community","use","edit","write","read","gh","Bash","first","publish","git","plugin","2026-11-10 10:12:30",false,"---\nname: obsidian-deploy-integration\ndescription: |\n  Publish Obsidian plugins to the community plugin directory.\n  Use when releasing your first plugin, updating existing plugins,\n  or managing the community plugin submission process.\n  Trigger with phrases like \"publish obsidian plugin\", \"obsidian community plugins\",\n  \"submit obsidian plugin\", \"obsidian plugin directory\".\nallowed-tools: Read, Write, Edit, Bash(git:*), Bash(gh:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\n---\n\n# Obsidian Deploy Integration\n\n## Overview\nComplete guide for publishing Obsidian plugins to the official community plugin directory.\n\n## Prerequisites\n- Completed and tested plugin\n- GitHub account\n- GitHub repository for your plugin\n- `gh` CLI installed (optional but recommended)\n\n## Community Plugin Directory Structure\n\n### Your Repository Requirements\n```\nyour-plugin-repo\u002F\n├── main.js              # Built plugin (required)\n├── manifest.json        # Plugin metadata (required)\n├── styles.css           # Optional styles\n├── README.md            # Documentation\n├── LICENSE              # License file\n└── .github\u002F\n    └── workflows\u002F       # CI\u002FCD workflows\n```\n\n### obsidian-releases Repository\n```\nobsidian-releases\u002F\n├── community-plugins.json    # Plugin registry\n└── community-css-themes.json # Theme registry\n```\n\n## Instructions\n\n### Step 1: Prepare Your Repository\n```bash\n# Ensure all required files are in repo root\nls -la main.js manifest.json\n\n# Validate manifest.json\ncat manifest.json\n# Should have: id, name, version, minAppVersion, description, author\n\n# Create GitHub release\ngh release create 1.0.0 \\\n  main.js \\\n  manifest.json \\\n  styles.css \\\n  --title \"v1.0.0\" \\\n  --notes \"Initial release\"\n```\n\n### Step 2: Fork obsidian-releases\n```bash\n# Fork the releases repository\ngh repo fork obsidianmd\u002Fobsidian-releases --clone\n\n# Navigate to fork\ncd obsidian-releases\n\n# Create branch for your submission\ngit checkout -b add-my-plugin\n```\n\n### Step 3: Add Plugin Entry\n```bash\n# Edit community-plugins.json\n# Add your plugin in alphabetical order by id\n\n# Example entry to add:\n{\n  \"id\": \"my-plugin-id\",\n  \"name\": \"My Plugin Name\",\n  \"author\": \"Your Name\",\n  \"description\": \"Brief description of what your plugin does\",\n  \"repo\": \"your-username\u002Fyour-repo-name\"\n}\n```\n\n### Step 4: Validate Entry\n```bash\n# Validate JSON syntax\ncat community-plugins.json | jq empty\n\n# Check your entry\ncat community-plugins.json | jq '.[] | select(.id == \"my-plugin-id\")'\n\n# Verify alphabetical ordering\ncat community-plugins.json | jq '.[].id' | sort -c\n```\n\n### Step 5: Submit Pull Request\n```bash\n# Commit changes\ngit add community-plugins.json\ngit commit -m \"Add my-plugin-id to community plugins\"\n\n# Push to your fork\ngit push origin add-my-plugin\n\n# Create PR\ngh pr create \\\n  --repo obsidianmd\u002Fobsidian-releases \\\n  --title \"Add my-plugin-id\" \\\n  --body \"## Plugin Submission\n\n**Plugin ID:** my-plugin-id\n**Plugin Name:** My Plugin Name\n**Repository:** https:\u002F\u002Fgithub.com\u002Fyour-username\u002Fyour-repo-name\n\n### Description\nBrief description of what the plugin does and why it's useful.\n\n### Checklist\n- [x] Plugin works on desktop (Windows, macOS, Linux)\n- [x] Plugin works on mobile (iOS, Android) or is marked desktop-only\n- [x] README.md explains installation and usage\n- [x] No console errors during normal operation\n- [x] Follows Obsidian plugin guidelines\n\n### Screenshots\n[Include screenshots if visual]\n\"\n```\n\n### Step 6: Post-Submission Process\n```markdown\n## After Submitting\n\n### Review Process\n1. **Automated checks** run within minutes\n2. **Manual review** by Obsidian team (1-7 days typically)\n3. **Feedback** may be provided via PR comments\n4. **Approval** leads to automatic publication\n\n### Common Review Feedback\n- Missing README documentation\n- Console.log statements in production code\n- Hardcoded API keys or sensitive data\n- Missing error handling\n- Incompatibility with mobile\n\n### Responding to Feedback\n1. Make requested changes in your plugin repo\n2. Create new release with fixes\n3. Comment on PR when ready for re-review\n```\n\n### Step 7: Post-Publication Maintenance\n```bash\n# After approval, your plugin is live!\n\n# For updates, just create new GitHub releases\ngh release create 1.0.1 \\\n  main.js manifest.json styles.css \\\n  --title \"v1.0.1\" \\\n  --notes \"Bug fixes and improvements\"\n\n# Obsidian automatically picks up new releases\n# Users will see update notifications\n\n# For major updates, update community-plugins.json if needed\n# (usually only for name\u002Fdescription changes)\n```\n\n## Output\n- Plugin repository properly structured\n- GitHub release created\n- Pull request submitted to obsidian-releases\n- Plugin published to community directory\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| PR validation fails | JSON syntax error | Validate with `jq` |\n| Plugin not found | Wrong repo path | Check repo URL exactly matches |\n| Release not picked up | No GitHub release | Create release with required files |\n| Mobile crash | Desktop-only API | Set `isDesktopOnly: true` |\n\n## Examples\n\n### Updating Plugin Description\n```bash\n# If you need to update name\u002Fdescription after publication\n# Edit community-plugins.json in your fork\n\n# Create PR with changes\ngh pr create \\\n  --repo obsidianmd\u002Fobsidian-releases \\\n  --title \"Update my-plugin-id description\" \\\n  --body \"Updating plugin description to better reflect new features.\"\n```\n\n### Complete Submission Script\n```bash\n#!\u002Fbin\u002Fbash\n# submit-plugin.sh\n\nPLUGIN_ID=\"my-plugin\"\nPLUGIN_NAME=\"My Plugin\"\nAUTHOR=\"Your Name\"\nDESCRIPTION=\"Plugin description\"\nREPO=\"username\u002Frepo-name\"\n\n# Fork and clone obsidian-releases\ngh repo fork obsidianmd\u002Fobsidian-releases --clone\ncd obsidian-releases\n\n# Create branch\ngit checkout -b add-$PLUGIN_ID\n\n# Add entry (using jq to maintain proper format)\njq --arg id \"$PLUGIN_ID\" \\\n   --arg name \"$PLUGIN_NAME\" \\\n   --arg author \"$AUTHOR\" \\\n   --arg desc \"$DESCRIPTION\" \\\n   --arg repo \"$REPO\" \\\n   '. += [{\"id\": $id, \"name\": $name, \"author\": $author, \"description\": $desc, \"repo\": $repo}] | sort_by(.id)' \\\n   community-plugins.json > tmp.json && mv tmp.json community-plugins.json\n\n# Commit and push\ngit add community-plugins.json\ngit commit -m \"Add $PLUGIN_ID\"\ngit push origin add-$PLUGIN_ID\n\n# Create PR\ngh pr create --repo obsidianmd\u002Fobsidian-releases \\\n  --title \"Add $PLUGIN_ID\" \\\n  --body \"Plugin submission for $PLUGIN_NAME\"\n\necho \"PR submitted! Check: https:\u002F\u002Fgithub.com\u002Fobsidianmd\u002Fobsidian-releases\u002Fpulls\"\n```\n\n### BRAT Beta Distribution\n```markdown\n## Pre-Release Distribution via BRAT\n\nFor beta testing before community submission:\n\n1. User installs BRAT plugin\n2. BRAT Settings > Add Beta Plugin\n3. Enter: `your-username\u002Fyour-repo-name`\n4. BRAT installs directly from your repo\n\nNo community-plugins.json entry needed for BRAT!\n```\n\n## Resources\n- [Plugin Submission Guidelines](https:\u002F\u002Fdocs.obsidian.md\u002FPlugins\u002FReleasing\u002FSubmit+your+plugin)\n- [obsidian-releases Repository](https:\u002F\u002Fgithub.com\u002Fobsidianmd\u002Fobsidian-releases)\n- [Plugin Guidelines](https:\u002F\u002Fdocs.obsidian.md\u002FPlugins\u002FReleasing\u002FPlugin+guidelines)\n- [BRAT Plugin](https:\u002F\u002Fgithub.com\u002FTfTHacker\u002Fobsidian42-brat)\n\n## Next Steps\nFor event handling patterns, see `obsidian-webhooks-events`.\n","# Obsidian Deploy Integration\n\n## Overview\nComplete guide for publishing Obsidian plugins to the official community plugin directory.\n\n## Prerequisites\n- Completed and tested plugin\n- GitHub account\n- GitHub repository for your plugin\n- `gh` CLI installed (optional but recommended)\n\n## Community Plugin Directory Structure\n\n### Your Repository Requirements\n```\nyour-plugin-repo\u002F\n├── main.js              # Built plugin (required)\n├── manifest.json        # Plugin metadata (required)\n├── styles.css           # Optional styles\n├── README.md            # Documentation\n├── LICENSE              # License file\n└── .github\u002F\n    └── workflows\u002F       # CI\u002FCD workflows\n```\n\n### obsidian-releases Repository\n```\nobsidian-releases\u002F\n├── community-plugins.json    # Plugin registry\n└── community-css-themes.json # Theme registry\n```\n\n## Instructions\n\n### Step 1: Prepare Your Repository\n```bash\n# Ensure all required files are in repo root\nls -la main.js manifest.json\n\n# Validate manifest.json\ncat manifest.json\n# Should have: id, name, version, minAppVersion, description, author\n\n# Create GitHub release\ngh release create 1.0.0 \\\n  main.js \\\n  manifest.json \\\n  styles.css \\\n  --title \"v1.0.0\" \\\n  --notes \"Initial release\"\n```\n\n### Step 2: Fork obsidian-releases\n```bash\n# Fork the releases repository\ngh repo fork obsidianmd\u002Fobsidian-releases --clone\n\n# Navigate to fork\ncd obsidian-releases\n\n# Create branch for your submission\ngit checkout -b add-my-plugin\n```\n\n### Step 3: Add Plugin Entry\n```bash\n# Edit community-plugins.json\n# Add your plugin in alphabetical order by id\n\n# Example entry to add:\n{\n  \"id\": \"my-plugin-id\",\n  \"name\": \"My Plugin Name\",\n  \"author\": \"Your Name\",\n  \"description\": \"Brief description of what your plugin does\",\n  \"repo\": \"your-username\u002Fyour-repo-name\"\n}\n```\n\n### Step 4: Validate Entry\n```bash\n# Validate JSON syntax\ncat community-plugins.json | jq empty\n\n# Check your entry\ncat community-plugins.json | jq '.[] | select(.id == \"my-plugin-id\")'\n\n# Verify alphabetical ordering\ncat community-plugins.json | jq '.[].id' | sort -c\n```\n\n### Step 5: Submit Pull Request\n```bash\n# Commit changes\ngit add community-plugins.json\ngit commit -m \"Add my-plugin-id to community plugins\"\n\n# Push to your fork\ngit push origin add-my-plugin\n\n# Create PR\ngh pr create \\\n  --repo obsidianmd\u002Fobsidian-releases \\\n  --title \"Add my-plugin-id\" \\\n  --body \"## Plugin Submission\n\n**Plugin ID:** my-plugin-id\n**Plugin Name:** My Plugin Name\n**Repository:** https:\u002F\u002Fgithub.com\u002Fyour-username\u002Fyour-repo-name\n\n### Description\nBrief description of what the plugin does and why it's useful.\n\n### Checklist\n- [x] Plugin works on desktop (Windows, macOS, Linux)\n- [x] Plugin works on mobile (iOS, Android) or is marked desktop-only\n- [x] README.md explains installation and usage\n- [x] No console errors during normal operation\n- [x] Follows Obsidian plugin guidelines\n\n### Screenshots\n[Include screenshots if visual]\n\"\n```\n\n### Step 6: Post-Submission Process\n```markdown\n## After Submitting\n\n### Review Process\n1. **Automated checks** run within minutes\n2. **Manual review** by Obsidian team (1-7 days typically)\n3. **Feedback** may be provided via PR comments\n4. **Approval** leads to automatic publication\n\n### Common Review Feedback\n- Missing README documentation\n- Console.log statements in production code\n- Hardcoded API keys or sensitive data\n- Missing error handling\n- Incompatibility with mobile\n\n### Responding to Feedback\n1. Make requested changes in your plugin repo\n2. Create new release with fixes\n3. Comment on PR when ready for re-review\n```\n\n### Step 7: Post-Publication Maintenance\n```bash\n# After approval, your plugin is live!\n\n# For updates, just create new GitHub releases\ngh release create 1.0.1 \\\n  main.js manifest.json styles.css \\\n  --title \"v1.0.1\" \\\n  --notes \"Bug fixes and improvements\"\n\n# Obsidian automatically picks up new releases\n# Users will see update notifications\n\n# For major updates, update community-plugins.json if needed\n# (usually only for name\u002Fdescription changes)\n```\n\n## Output\n- Plugin repository properly structured\n- GitHub release created\n- Pull request submitted to obsidian-releases\n- Plugin published to community directory\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| PR validation fails | JSON syntax error | Validate with `jq` |\n| Plugin not found | Wrong repo path | Check repo URL exactly matches |\n| Release not picked up | No GitHub release | Create release with required files |\n| Mobile crash | Desktop-only API | Set `isDesktopOnly: true` |\n\n## Examples\n\n### Updating Plugin Description\n```bash\n# If you need to update name\u002Fdescription after publication\n# Edit community-plugins.json in your fork\n\n# Create PR with changes\ngh pr create \\\n  --repo obsidianmd\u002Fobsidian-releases \\\n  --title \"Update my-plugin-id description\" \\\n  --body \"Updating plugin description to better reflect new features.\"\n```\n\n### Complete Submission Script\n```bash\n#!\u002Fbin\u002Fbash\n# submit-plugin.sh\n\nPLUGIN_ID=\"my-plugin\"\nPLUGIN_NAME=\"My Plugin\"\nAUTHOR=\"Your Name\"\nDESCRIPTION=\"Plugin description\"\nREPO=\"username\u002Frepo-name\"\n\n# Fork and clone obsidian-releases\ngh repo fork obsidianmd\u002Fobsidian-releases --clone\ncd obsidian-releases\n\n# Create branch\ngit checkout -b add-$PLUGIN_ID\n\n# Add entry (using jq to maintain proper format)\njq --arg id \"$PLUGIN_ID\" \\\n   --arg name \"$PLUGIN_NAME\" \\\n   --arg author \"$AUTHOR\" \\\n   --arg desc \"$DESCRIPTION\" \\\n   --arg repo \"$REPO\" \\\n   '. += [{\"id\": $id, \"name\": $name, \"author\": $author, \"description\": $desc, \"repo\": $repo}] | sort_by(.id)' \\\n   community-plugins.json > tmp.json && mv tmp.json community-plugins.json\n\n# Commit and push\ngit add community-plugins.json\ngit commit -m \"Add $PLUGIN_ID\"\ngit push origin add-$PLUGIN_ID\n\n# Create PR\ngh pr create --repo obsidianmd\u002Fobsidian-releases \\\n  --title \"Add $PLUGIN_ID\" \\\n  --body \"Plugin submission for $PLUGIN_NAME\"\n\necho \"PR submitted! Check: https:\u002F\u002Fgithub.com\u002Fobsidianmd\u002Fobsidian-releases\u002Fpulls\"\n```\n\n### BRAT Beta Distribution\n```markdown\n## Pre-Release Distribution via BRAT\n\nFor beta testing before community submission:\n\n1. User installs BRAT plugin\n2. BRAT Settings > Add Beta Plugin\n3. Enter: `your-username\u002Fyour-repo-name`\n4. BRAT installs directly from your repo\n\nNo community-plugins.json entry needed for BRAT!\n```\n\n## Resources\n- [Plugin Submission Guidelines](https:\u002F\u002Fdocs.obsidian.md\u002FPlugins\u002FReleasing\u002FSubmit+your+plugin)\n- [obsidian-releases Repository](https:\u002F\u002Fgithub.com\u002Fobsidianmd\u002Fobsidian-releases)\n- [Plugin Guidelines](https:\u002F\u002Fdocs.obsidian.md\u002FPlugins\u002FReleasing\u002FPlugin+guidelines)\n- [BRAT Plugin](https:\u002F\u002Fgithub.com\u002FTfTHacker\u002Fobsidian42-brat)\n\n## Next Steps\nFor event handling patterns, see `obsidian-webhooks-events`.\n",{"name":5,"author":52,"license":15,"version":53,"description":54,"allowed-tools":55},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Publish Obsidian plugins to the community plugin directory.\nUse when releasing your first plugin, updating existing plugins,\nor managing the community plugin submission process.\nTrigger with phrases like \"publish obsidian plugin\", \"obsidian community plugins\",\n\"submit obsidian plugin\", \"obsidian plugin directory\".\n","Read, Write, Edit, Bash(git:*), Bash(gh:*)","main","90b50ed0778745a80fd5bfb13b1843d45b9e82f7","tests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fobsidian-pack\u002Fskills\u002Fobsidian-deploy-integration",231,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust","https:\u002F\u002Fgithub.com\u002FDicklesworthstone","https:\u002F\u002Fwww.jeffreyemanuel.com\u002F","Building in NY","2026-11-11 01:23:40",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add Dicklesworthstone\u002Fpi_agent_rust --skill obsidian-deploy-integration",{"tool":71,"command":72},"bunx","bunx skills add Dicklesworthstone\u002Fpi_agent_rust --skill obsidian-deploy-integration",{"tool":74,"command":75},"pnpm","pnpm dlx skills add Dicklesworthstone\u002Fpi_agent_rust --skill obsidian-deploy-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fobsidian-pack\u002Fskills\u002Fobsidian-deploy-integration\u002FSKILL.md",true,[],[80,118,142,168,194,216],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":91,"publishedAt":47},"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",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,37,110,111,112,113,114,115,116,117],"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","for","jsx","suite",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":129,"publishedAt":47},"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",[125,128],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},[130,131,132,97,133,134,93,135,136,137,107,138,139,140,141,32,115],"testing","webapp testing","webapp","screenshots","playwright","debugging","toolkit","browser","logs","applications","behavior","local",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":47},"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",[],[150,151,152,153,154,155,156,157,37,158,159,160,161,162,163,164,32,165,166,167,115,28],"analysis","neuropixels analysis","spike","metrics","data","open","quality","user","recordings","Neural","motion","visual","quality metrics","unit","sorting","curation","recording","load",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":172,"sourceHtmlUrl":173,"categories":174,"keywords":178,"publishedAt":47},"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",[175],{"categoryNo":176,"categoryName":177,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[179,180,181,182,183,184,185,186,187,188,189,190,191,192,32,115,31,28,193],"skill creator","creator","workflows","create","update","capabilities","knowledge","tool","integrations","specialized","guide","new skill","existing skill","users","new",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":198,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":47},"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",[201],{"categoryNo":176,"categoryName":177,"taxonomyType":21,"taxonomyTypeDesc":22},[196,203,204,205,206,207,208,137,209,210,37,211,212,213,214,115,215],"google","browser automation","gemini","automation","auth","code","library","management","only","document","query","Citation","source",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":220,"sourceHtmlUrl":221,"categories":222,"keywords":229,"publishedAt":47},"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",[223,226],{"categoryNo":224,"categoryName":225,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":227,"categoryName":228,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[230,231,232,180,233,108,234,235,185,37,236,192,237,238,239,115,240,28],"slack gif creator","slack","gif","validation","constraints","Animation","me","make","Utilities","concepts","request"]