Agent skill

Chrome Extension Development

by Mindrally in Mindrally/skills

Expert guidelines for Chrome extension development with Manifest V3, covering security, performance, and best practices.

Apache-2.0Auto-check passedDevelopment

Install Chrome Extension Development

skills CLI
$ npx skills add Mindrally/skills --skill chrome-extension-development -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Mindrally/skills chrome-extension-development --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Mindrally/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/chrome-extension-development .claude/skills/chrome-extension-development && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
chrome-extension-development
GitHub stars
268
Token cost
~1.7k tokens
SKILL.md length
527 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
Apache-2.0

At a glance

Expert guidelines for Chrome extension development with Manifest V3, covering security, performance, and best practices.

  • Works in 8 steps: Initialize the project — Create the… → Configure the manifest — Define… → Implement the background service worker… → …
  • Building browser extensions
  • SKILL.md covers Workflow: Building a Chrome…, Example: Minimal Manifest V3…, Example: Background Service… and Code Style and Structure, plus 11 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Chrome Extension Development is an agent skill from Mindrally/skills. Expert guidelines for Chrome extension development with Manifest V3, covering security, performance, and best practices. Use when building browser extensions, creating popup UIs, implementing content scripts, working with Chrome APIs, managing extension permissions, or publishing to Chrome Web Store.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Browser extensions. It works with Chrome Extensions. The repository describes itself as: 255+ Claude Code skills converted from Cursor rules. Expert coding guidelines for every major framework and language. The licence is Apache-2.0.

When your agent uses it

  • Building browser extensions
  • Creating popup UIs
  • Implementing content scripts
  • Working with Chrome APIs

Example prompts

  • “/chrome-extension-development”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Initialize the project — Create the directory structure with manifest.json, background service worker, content scripts, and popup files.
  2. Configure the manifest — Define permissions, content script matches, service worker registration, and action settings in Manifest V3 format.
  3. Implement the background service worker — Set up event listeners for extension lifecycle, messaging, and alarms using the chrome.* API.
  4. Build content scripts — Write scripts that interact with web page DOM, communicate with the background worker via…
  5. Create the popup UI — Design the popup HTML/CSS and wire up interactivity with the background and content scripts.
  6. Add storage and state management — Use chrome.storage.local or chrome.storage.sync to persist user settings and extension state.
  7. Test and debug — Load the extension unpacked via chrome://extensions, use Chrome DevTools to inspect the service worker and content…
  8. Package and publish — Prepare store assets (icons, screenshots, description), create a privacy policy, and submit to the Chrome Web Store.

What it can do on your machine

Read from SKILL.md and the folder at commit 9718410. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json and typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Chrome Extension Development loads about 1.7k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 527 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Mindrally/skills at commit 9718410, republished under its Apache-2.0 licence (© Mindrally). 527 words, ~1,654 tokens.

Download SKILL.mdSave it as .claude/skills/chrome-extension-development/SKILL.md (or your agent's skills folder).
name
chrome-extension-development
description
Expert guidelines for Chrome extension development with Manifest V3, covering security, performance, and best practices. Use when building browser extensions, creating popup UIs, implementing content scripts, working with Chrome APIs, managing extension permissions, or publishing to Chrome Web Store.

Chrome Extension Development

This skill provides expert-level guidance for Chrome extension development, covering JavaScript/TypeScript, browser extension APIs, and modern web development practices.

Workflow: Building a Chrome Extension from Scratch

  1. Initialize the project — Create the directory structure with manifest.json, background service worker, content scripts, and popup files.
  2. Configure the manifest — Define permissions, content script matches, service worker registration, and action settings in Manifest V3 format.
  3. Implement the background service worker — Set up event listeners for extension lifecycle, messaging, and alarms using the chrome.* API.
  4. Build content scripts — Write scripts that interact with web page DOM, communicate with the background worker via chrome.runtime.sendMessage, and respect CSP.
  5. Create the popup UI — Design the popup HTML/CSS and wire up interactivity with the background and content scripts.
  6. Add storage and state management — Use chrome.storage.local or chrome.storage.sync to persist user settings and extension state.
  7. Test and debug — Load the extension unpacked via chrome://extensions, use Chrome DevTools to inspect the service worker and content scripts, and run unit tests.
  8. Package and publish — Prepare store assets (icons, screenshots, description), create a privacy policy, and submit to the Chrome Web Store.

Example: Minimal Manifest V3 Configuration

json
{
  "manifest_version": 3,
  "name": "My Extension",
  "version": "1.0.0",
  "description": "A sample Chrome extension using Manifest V3",
  "permissions": ["storage", "activeTab"],
  "action": {
    "default_popup": "popup/popup.html",
    "default_icon": {
      "16": "icons/icon16.png",
      "48": "icons/icon48.png",
      "128": "icons/icon128.png"
    }
  },
  "background": {
    "service_worker": "background/service-worker.js",
    "type": "module"
  },
  "content_scripts": [
    {
      "matches": ["https://*.example.com/*"],
      "js": ["content/content-script.js"],
      "css": ["content/styles.css"]
    }
  ]
}

Example: Background Service Worker with Messaging

typescript
// background/service-worker.ts

// Listen for extension install or update
chrome.runtime.onInstalled.addListener((details) => {
  if (details.reason === 'install') {
    chrome.storage.local.set({ initialized: true, count: 0 });
    console.log('Extension installed');
  }
});

// Handle messages from content scripts or popup
chrome.runtime.onMessage.addListener(
  (message: { type: string; payload?: unknown }, sender, sendResponse) => {
    if (message.type === 'GET_COUNT') {
      chrome.storage.local.get('count', (result) => {
        sendResponse({ count: result.count ?? 0 });
      });
      return true; // keep message channel open for async response
    }

    if (message.type === 'INCREMENT') {
      chrome.storage.local.get('count', (result) => {
        const newCount = (result.count ?? 0) + 1;
        chrome.storage.local.set({ count: newCount }, () => {
          sendResponse({ count: newCount });
        });
      });
      return true;
    }
  }
);

// Schedule periodic tasks with chrome.alarms
chrome.alarms.create('sync-data', { periodInMinutes: 30 });
chrome.alarms.onAlarm.addListener((alarm) => {
  if (alarm.name === 'sync-data') {
    console.log('Running scheduled sync');
  }
});

Code Style and Structure

  • Write clear, modular TypeScript code with proper type definitions
  • Follow functional programming patterns; avoid classes
  • Use descriptive variable names (e.g., isLoading, hasPermission)
  • Structure files logically: popup, background, content scripts, utils
  • Implement proper error handling and logging
  • Document code with JSDoc comments

Architecture and Best Practices

  • Strictly follow Manifest V3 specifications
  • Divide responsibilities between background, content scripts and popup
  • Configure permissions following the principle of least privilege
  • Use modern build tools (webpack/vite) for development
  • Implement proper version control and change management

Chrome API Usage

  • Use chrome.* APIs correctly (storage, tabs, runtime, etc.)
  • Handle asynchronous operations with Promises
  • Use Service Worker for background scripts (MV3 requirement)
  • Implement chrome.alarms for scheduled tasks
  • Use chrome.action API for browser actions
  • Handle offline functionality gracefully
Show full SKILL.md (203 more words)Show less

Security and Privacy

  • Implement Content Security Policy (CSP)
  • Handle user data securely
  • Prevent XSS and injection attacks
  • Use secure messaging between components
  • Handle cross-origin requests safely
  • Implement secure data encryption
  • Follow web_accessible_resources best practices

Performance and Optimization

  • Minimize resource usage and avoid memory leaks
  • Optimize background script performance
  • Implement proper caching mechanisms
  • Handle asynchronous operations efficiently
  • Monitor and optimize CPU/memory usage

UI and User Experience

  • Follow Material Design guidelines
  • Implement responsive popup windows
  • Provide clear user feedback
  • Support keyboard navigation
  • Ensure proper loading states
  • Add appropriate animations

Internationalization

  • Use chrome.i18n API for translations
  • Follow _locales structure
  • Support RTL languages
  • Handle regional formats

Accessibility

  • Implement ARIA labels
  • Ensure sufficient color contrast
  • Support screen readers
  • Add keyboard shortcuts

Testing and Debugging

  • Use Chrome DevTools effectively
  • Write unit and integration tests
  • Test cross-browser compatibility
  • Monitor performance metrics
  • Handle error scenarios

Publishing and Maintenance

  • Prepare store listings and screenshots
  • Write clear privacy policies
  • Implement update mechanisms
  • Handle user feedback
  • Maintain documentation

Follow Official Documentation

  • Refer to Chrome Extension documentation
  • Stay updated with Manifest V3 changes
  • Follow Chrome Web Store guidelines
  • Monitor Chrome platform updates

Output Expectations

  • Provide clear, working code examples
  • Include necessary error handling
  • Follow security best practices
  • Ensure cross-browser compatibility
  • Write maintainable and scalable code

© Mindrally, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in chrome-extension-development of Mindrally/skills.

Open the folder on GitHubat commit 9718410

Compare with similar skills

Chrome Extension Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Chrome Extension Development compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Chrome Extension Development this skillMindrally/skills268—~1.7kAutomated safety check: PassApache-2.0
Wxt Browser Extensionsvantezzen/skip-silence4682 repos~1.9kAutomated safety check: PassMIT
Kimi WebbridgeMoonshotAI/kimi-code7.8k—~3.6kAutomated safety check: PassMIT
Repomix Browser Extension Developeryamadashy/repomix29k1 repos~288Automated safety check: PassMIT
Deepseek Automationzhu1090093659/deepseek-pp1.9k—~2.1kAutomated safety check: NotesApache-2.0
Live Extension UI Automationqixing-jk/all-api-hub4.9k—~2.6kAutomated safety check: PassAGPL-3.0

Similar skills

  • Wxt Browser Extensions

    vantezzen/skip-silence

    WXT browser extension performance optimization guidelines. An agent skill from vantezzen/skip-silence.

    468 GitHub starsUsed in 2 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Kimi Webbridge

    MoonshotAI/kimi-code

    Kimi Browser Extension(Kimi 浏览器扩展,原 Kimi WebBridge)lets AI control the user's real browser — navigate, click, type, read, screenshot, and interact with any website using the user's actual login…

    7.8k GitHub stars~3.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content…

    29k GitHub starsUsed in 1 repo~288 tokens
    DevelopmentAuto-check passed
  • Deepseek Automation

    zhu1090093659/deepseek-pp

    A skill your agent uses when implementing, resuming, reviewing, or verifying the DeepSeek++ Codex-style automation feature in this repository.

    1.9k GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes
  • Live Extension UI Automation

    qixing-jk/all-api-hub

    Control, debug, and test the live dev browser extension UI (Options, Popup, Sidepanel) via CDP with persistent login states and accounts.

    4.9k GitHub stars~2.6k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Cuts a new Knockoff release by bumping the version, rolling release notes, tagging and shipping to the Chrome, Firefox and Apple stores with a per-store report.

    1.9k GitHub stars~1.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes

More from Mindrally/skills

All 34 skills in this repo
  • Analytics Data Analysis

    Mindrally/skills

    Best practices for analytics, data analysis, and visualization using Python, pandas, matplotlib, seaborn, and Jupyter notebooks.

    268 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Best practices for AutoML and hyperparameter search with Optuna, Ray Tune, and PyCaret, covering search-space design, validation splits, and leakage prevention.

    268 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Blender Python Addon

    Mindrally/skills

    Best practices for writing Blender Python add-ons using the bpy API, covering operators, panels, properties, registration, and API-safe scripting.

    268 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Clean Code

    Mindrally/skills

    Clean, maintainable, human-readable code principles combined with anti-over-engineering discipline: naming, single responsibility, DRY, and scoping changes to exactly what was requested.

    268 GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Design Systems

    Mindrally/skills

    Comprehensive design system guidelines for building consistent, accessible, and scalable component libraries.

    268 GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Embedded Stm32

    Mindrally/skills

    Best practices for embedded C/C++ development on STM32 microcontrollers using the HAL, covering peripherals, DMA, interrupts, memory constraints, and hardware-focused testing.

    268 GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Chrome Extension Development

What does Chrome Extension Development do?

Expert guidelines for Chrome extension development with Manifest V3, covering security, performance, and best practices. Chrome Extension Development is an agent skill from Mindrally/skills. Expert guidelines for Chrome extension development with Manifest V3, covering security, performance, and best practices.

When should I use Chrome Extension Development?

Chrome Extension Development fits situations like: building browser extensions; creating popup UIs; implementing content scripts; working with Chrome APIs.

How do I install Chrome Extension Development in Claude Code?

Run `npx skills add Mindrally/skills --skill chrome-extension-development -a claude-code`. Or copy the skill folder (chrome-extension-development in Mindrally/skills) into .claude/skills/chrome-extension-development in your project. Claude Code loads it when a task matches its description.

How do I install Chrome Extension Development in Codex?

Run `npx skills add Mindrally/skills --skill chrome-extension-development -a codex`. Or copy the skill folder (chrome-extension-development in Mindrally/skills) into .agents/skills/chrome-extension-development in your project. Codex loads it when a task matches its description.

Can I use Chrome Extension Development in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mindrally/skills --skill chrome-extension-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chrome-extension-development, .gemini/skills/chrome-extension-development, .github/skills/chrome-extension-development and .opencode/skills/chrome-extension-development in your project.

What does Chrome Extension Development need to run?

SKILL.md names no scripts, command-line tools or credentials: Chrome Extension Development is instructions for the agent only.

Does Chrome Extension Development access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Chrome Extension Development safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Chrome Extension Development use?

Chrome Extension Development is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Chrome Extension Development use?

About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Chrome Extension Development?

Skills that share tags, products or a category with Chrome Extension Development: Wxt Browser Extensions (vantezzen/skip-silence, 468 stars), Kimi Webbridge (MoonshotAI/kimi-code, 7.8k stars), Repomix Browser Extension Developer (yamadashy/repomix, 29k stars) and Deepseek Automation (zhu1090093659/deepseek-pp, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chrome Extension Development?

Mindrally (a GitHub organization) maintains it in Mindrally/skills, which has 268 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on September 3, 2026.

Source: Mindrally/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.