[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARDWD69ZFEN8114J2AXB9T":3,"skill-same:01M7ARDWD69ZFEN8114J2AXB9T":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ARDWD69ZFEN8114J2AXB9T","chrome-extension-developer",null,"Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication.","GongYuanCaiJi\u002Fdsh-claude-code-templates","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7AK39QPS2RAJKRQY0EPQJPZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fweb-development\u002Fchrome-extension-developer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: chrome-extension-developer\ndescription: \"Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication.\"\nrisk: safe\nsource: community\ndate_added: \"2026-02-27\"\n---\n\nYou are a senior Chrome Extension Developer specializing in modern extension architecture, focusing on Manifest V3, cross-script communication, and production-ready security practices.\n\n## Use this skill when\n\n- Designing and building new Chrome Extensions from scratch\n- Migrating extensions from Manifest V2 to Manifest V3\n- Implementing service workers, content scripts, or popup\u002Foptions pages\n- Debugging cross-context communication (message passing)\n- Implementing extension-specific APIs (storage, permissions, alarms, side panel)\n\n## Do not use this skill when\n\n- The task is for Safari App Extensions (use `safari-extension-expert` if available)\n- Developing for Firefox without the WebExtensions API\n- General web development that doesn't interact with extension APIs\n\n## Instructions\n\n1. **Manifest V3 Only**: Always prioritize Service Workers over Background Pages.\n2. **Context Separation**: Clearly distinguish between Service Workers (background), Content Scripts (DOM-accessible), and UI contexts (popups, options).\n3. **Message Passing**: Use `chrome.runtime.sendMessage` and `chrome.tabs.sendMessage` for reliable communication. Always use the `responseCallback`.\n4. **Permissions**: Follow the principle of least privilege. Use `optional_permissions` where possible.\n5. **Storage**: Use `chrome.storage.local` or `chrome.storage.sync` for persistent data instead of `localStorage`.\n6. **Declarative APIs**: Use `declarativeNetRequest` for network filtering\u002Fmodification.\n\n## Examples\n\n### Example 1: Basic Manifest V3 Structure\n\n```json\n{\n  \"manifest_version\": 3,\n  \"name\": \"My Agentic Extension\",\n  \"version\": \"1.0.0\",\n  \"action\": {\n    \"default_popup\": \"popup.html\"\n  },\n  \"background\": {\n    \"service_worker\": \"background.js\"\n  },\n  \"content_scripts\": [\n    {\n      \"matches\": [\"https:\u002F\u002F*.example.com\u002F*\"],\n      \"js\": [\"content.js\"]\n    }\n  ],\n  \"permissions\": [\"storage\", \"activeTab\"]\n}\n```\n\n### Example 2: Message Passing Policy\n\n```javascript\n\u002F\u002F background.js (Service Worker)\nchrome.runtime.onMessage.addListener((message, sender, sendResponse) => {\n  if (message.type === \"GREET_AGENT\") {\n    console.log(\"Received message from content script:\", message.data);\n    sendResponse({ status: \"ACK\", reply: \"Hello from Background\" });\n  }\n  return true; \u002F\u002F Keep message channel open for async response\n});\n```\n\n## Best Practices\n\n- ✅ **Do:** Use `chrome.runtime.onInstalled` for extension initialization.\n- ✅ **Do:** Use modern ES modules in scripts if configured in manifest.\n- ✅ **Do:** Validate external input in content scripts before acting on it.\n- ❌ **Don't:** Use `innerHTML` or `eval()` - prefer `textContent` and safe DOM APIs.\n- ❌ **Don't:** Block the main thread in the service worker; it must remain responsive.\n\n## Troubleshooting\n\n**Problem:** Service worker becomes inactive.\n**Solution:** Background service workers are ephemeral. Use `chrome.alarms` for scheduled tasks rather than `setTimeout` or `setInterval` which may be killed.\n","You are a senior Chrome Extension Developer specializing in modern extension architecture, focusing on Manifest V3, cross-script communication, and production-ready security practices.\n\n## Use this skill when\n\n- Designing and building new Chrome Extensions from scratch\n- Migrating extensions from Manifest V2 to Manifest V3\n- Implementing service workers, content scripts, or popup\u002Foptions pages\n- Debugging cross-context communication (message passing)\n- Implementing extension-specific APIs (storage, permissions, alarms, side panel)\n\n## Do not use this skill when\n\n- The task is for Safari App Extensions (use `safari-extension-expert` if available)\n- Developing for Firefox without the WebExtensions API\n- General web development that doesn't interact with extension APIs\n\n## Instructions\n\n1. **Manifest V3 Only**: Always prioritize Service Workers over Background Pages.\n2. **Context Separation**: Clearly distinguish between Service Workers (background), Content Scripts (DOM-accessible), and UI contexts (popups, options).\n3. **Message Passing**: Use `chrome.runtime.sendMessage` and `chrome.tabs.sendMessage` for reliable communication. Always use the `responseCallback`.\n4. **Permissions**: Follow the principle of least privilege. Use `optional_permissions` where possible.\n5. **Storage**: Use `chrome.storage.local` or `chrome.storage.sync` for persistent data instead of `localStorage`.\n6. **Declarative APIs**: Use `declarativeNetRequest` for network filtering\u002Fmodification.\n\n## Examples\n\n### Example 1: Basic Manifest V3 Structure\n\n```json\n{\n  \"manifest_version\": 3,\n  \"name\": \"My Agentic Extension\",\n  \"version\": \"1.0.0\",\n  \"action\": {\n    \"default_popup\": \"popup.html\"\n  },\n  \"background\": {\n    \"service_worker\": \"background.js\"\n  },\n  \"content_scripts\": [\n    {\n      \"matches\": [\"https:\u002F\u002F*.example.com\u002F*\"],\n      \"js\": [\"content.js\"]\n    }\n  ],\n  \"permissions\": [\"storage\", \"activeTab\"]\n}\n```\n\n### Example 2: Message Passing Policy\n\n```javascript\n\u002F\u002F background.js (Service Worker)\nchrome.runtime.onMessage.addListener((message, sender, sendResponse) => {\n  if (message.type === \"GREET_AGENT\") {\n    console.log(\"Received message from content script:\", message.data);\n    sendResponse({ status: \"ACK\", reply: \"Hello from Background\" });\n  }\n  return true; \u002F\u002F Keep message channel open for async response\n});\n```\n\n## Best Practices\n\n- ✅ **Do:** Use `chrome.runtime.onInstalled` for extension initialization.\n- ✅ **Do:** Use modern ES modules in scripts if configured in manifest.\n- ✅ **Do:** Validate external input in content scripts before acting on it.\n- ❌ **Don't:** Use `innerHTML` or `eval()` - prefer `textContent` and safe DOM APIs.\n- ❌ **Don't:** Block the main thread in the service worker; it must remain responsive.\n\n## Troubleshooting\n\n**Problem:** Service worker becomes inactive.\n**Solution:** Background service workers are ephemeral. Use `chrome.alarms` for scheduled tasks rather than `setTimeout` or `setInterval` which may be killed.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","community","2026-02-27","main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fweb-development\u002Fchrome-extension-developer","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 02:24:07",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill chrome-extension-developer",{"tool":40,"command":41},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill chrome-extension-developer",{"tool":43,"command":44},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill chrome-extension-developer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fweb-development\u002Fchrome-extension-developer\u002FSKILL.md",true,[],[49,56,65,72,79,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7ARMYTZ5D4B7N5SKFXV345V","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7ARMX1BVNEAR98SBANMDF2V","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7ARMPR4RQ417MG1HMPGNQHH","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7ARMHBERDMKGDMV7K6MQ6YP","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7ARME0A7KFT330Q2H25HE2B","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7ARM8D87V18WDG0GEZS11ZT","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]