Index of every page on this site: llms.txt
All skills
davila7 avatar

/chrome-extension-developer

@053feb2
Run it yourself

Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication.

Use this Skill: https://skilld.dev/gh/davila7/claude-code-templates/chrome-extension-developer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈44 tokens for metadata: the name and description. ≈746 when used: this file.

Description uses 2.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈178 characters, or 2.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

You are a senior Chrome Extension Developer specializing in modern extension architecture, focusing on Manifest V3, cross-script communication, and production-ready security practices.

Use this skill when

  • Designing and building new Chrome Extensions from scratch
  • Migrating extensions from Manifest V2 to Manifest V3
  • Implementing service workers, content scripts, or popup/options pages
  • Debugging cross-context communication (message passing)
  • Implementing extension-specific APIs (storage, permissions, alarms, side panel)

Do not use this skill when

  • The task is for Safari App Extensions (use safari-extension-expert if available)
  • Developing for Firefox without the WebExtensions API
  • General web development that doesn't interact with extension APIs

Instructions

  1. Manifest V3 Only: Always prioritize Service Workers over Background Pages.
  2. Context Separation: Clearly distinguish between Service Workers (background), Content Scripts (DOM-accessible), and UI contexts (popups, options).
  3. Message Passing: Use chrome.runtime.sendMessage and chrome.tabs.sendMessage for reliable communication. Always use the responseCallback.
  4. Permissions: Follow the principle of least privilege. Use optional_permissions where possible.
  5. Storage: Use chrome.storage.local or chrome.storage.sync for persistent data instead of localStorage.
  6. Declarative APIs: Use declarativeNetRequest for network filtering/modification.

Examples

Example 1: Basic Manifest V3 Structure

{
  "manifest_version": 3,
  "name": "My Agentic Extension",
  "version": "1.0.0",
  "action": {
    "default_popup": "popup.html"
  },
  "background": {
    "service_worker": "background.js"
  },
  "content_scripts": [
    {
      "matches": ["https://*.example.com/*"],
      "js": ["content.js"]
    }
  ],
  "permissions": ["storage", "activeTab"]
}

Example 2: Message Passing Policy

// background.js (Service Worker)
chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
  if (message.type === "GREET_AGENT") {
    console.log("Received message from content script:", message.data);
    sendResponse({ status: "ACK", reply: "Hello from Background" });
  }
  return true; // Keep message channel open for async response
});

Best Practices

  • ✅ Do: Use chrome.runtime.onInstalled for extension initialization.
  • ✅ Do: Use modern ES modules in scripts if configured in manifest.
  • ✅ Do: Validate external input in content scripts before acting on it.
  • ❌ Don't: Use innerHTML or eval() - prefer textContent and safe DOM APIs.
  • ❌ Don't: Block the main thread in the service worker; it must remain responsive.

Troubleshooting

Problem: Service worker becomes inactive. Solution: Background service workers are ephemeral. Use chrome.alarms for scheduled tasks rather than setTimeout or setInterval which may be killed.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts6d3 checks · Risk SAFE
  • Gen Agent Trust Hub6d

    No security issues detected. The skill provides standard documentation and best practices for Chrome extension development, emphasizing modern Manifest V3 security standards.

  • Socket6d

    No alerts

  • Snyk6d

    Risk: LOW · No issues

Signed by skilld at 053feb2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
metadata
{
  "risk": "safe",
  "source": "community",
  "date_added": "2026-02-27"
}

README badge

README badge for davila7/claude-code-templates/chrome-extension-developer