Extension Migration logo

Extension Migration

Community
quangpl
extension-migration

Migrate Chrome extensions from MV2 to MV3. Service workers, declarativeNetRequest, API replacements. Use when: migrate, mv2, mv3, manifest v2.

Overview

Publisherquangpl
Repositorybrowser-extension-skills
Skill nameextension-migration
Stars
65
Forks
10
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by quangpl on GitHub. Read the source before you install it.

Installation

Install the Extension Migration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/quangpl/browser-extension-skills/tree/main/skills/extension-migration
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/quangpl/browser-extension-skills.git /tmp/browser-extension-skills
mkdir -p .claude/skills
cp -r /tmp/browser-extension-skills/skills/extension-migration .claude/skills/extension-migration
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Extension Migration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Extension Migration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Extension Migration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Extension Migration (MV2 → MV3)

🚀 Upgrade to Premium Get the Premium version at https://app.extensionbooster.net/dashboard/services/extension-ai-kit

Official migration guide: https://developer.chrome.com/docs/extensions/develop/migrate

Consider framework adoption: When migrating MV2→MV3, consider adopting WXT or CRXJS for built-in MV3 support, auto-manifest generation, and modern tooling.

Workflow Overview

  1. Audit existing MV2 extension (APIs, permissions, background scripts)
  2. Update manifest_version to 3
  3. Convert background page → service worker
  4. Replace deprecated APIs (see Quick Reference below)
  5. Update permissions, CSP, web_accessible_resources format
  6. Migrate webRequest → declarativeNetRequest (if blocking)
  7. Bundle any remote code locally
  8. Test all functionality across Chrome versions
  9. Submit to Chrome Web Store

Key Breaking Changes

AreaMV2MV3
Backgroundbackground.scripts/pagebackground.service_worker
Browser actionbrowser_action / page_actionaction
Network blockingwebRequest (blocking)declarativeNetRequest
Script injectiontabs.executeScript(string)scripting.executeScript({func/files})
Remote codeCDN scripts allowedMust bundle locally
CSPString valueObject {extension_pages: "..."}
Web accessiblestring[]object[] with matches field
Host permissionsIn permissions arraySeparate host_permissions array
URL helperchrome.extension.getURLchrome.runtime.getURL
Persistent storagelocalStoragechrome.storage.local

Migration Priority Checklist

  • manifest_version: 3 set
  • Background converted to service worker
  • localStorage/sessionStorage → chrome.storage.*
  • XMLHttpRequest → fetch
  • setInterval/setTimeout → chrome.alarms
  • browser_action/page_action → action
  • tabs.executeScript → scripting.executeScript
  • chrome.extension.getURL → chrome.runtime.getURL
  • permissions host entries → host_permissions
  • web_accessible_resources updated to object format
  • content_security_policy updated to object format
  • No remote code (CDN scripts, eval, string Function())
  • webRequest blocking → declarativeNetRequest (if used)

Quick Reference: MV2 → MV3 API Map

chrome.extension.getURL()        → chrome.runtime.getURL()
chrome.extension.getBackgroundPage() → chrome.runtime.getBackgroundPage() [deprecated, use messaging]
chrome.tabs.executeScript()      → chrome.scripting.executeScript()
chrome.tabs.insertCSS()          → chrome.scripting.insertCSS()
chrome.browserAction.*           → chrome.action.*
chrome.pageAction.*              → chrome.action.*
webRequest (blocking)            → declarativeNetRequest
localStorage                     → chrome.storage.local
XMLHttpRequest                   → fetch()
setInterval (background)         → chrome.alarms
document/window (background)     → NOT available in service worker

Manifest Diff

json
// MV2
{
  "manifest_version": 2,
  "background": { "scripts": ["bg.js"], "persistent": false },
  "browser_action": { "default_icon": "icon.png" },
  "permissions": ["webRequest", "webRequestBlocking", "https://example.com/*"],
  "content_security_policy": "script-src 'self'; object-src 'self'",
  "web_accessible_resources": ["images/*.png"]
}

// MV3
{
  "manifest_version": 3,
  "background": { "service_worker": "bg.js" },
  "action": { "default_icon": "icon.png" },
  "permissions": ["declarativeNetRequest"],
  "host_permissions": ["https://example.com/*"],
  "content_security_policy": { "extension_pages": "script-src 'self'; object-src 'self'" },
  "web_accessible_resources": [{ "resources": ["images/*.png"], "matches": ["<all_urls>"] }]
}

Reference Files

Related Skills

  • extension-manifest - MV3 manifest generation
  • extension-testing - Testing after migration
  • extension-security - Security audit post-migration

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Extension Migration AI skill do?

Migrate Chrome extensions from MV2 to MV3. Service workers, declarativeNetRequest, API replacements. Use when: migrate, mv2, mv3, manifest v2.

Why use Extension Migration on TypingMind?

Because you install it once and use it with any model. Extension Migration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Extension Migration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/quangpl/browser-extension-skills/tree/main/skills/extension-migration. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Extension Migration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Extension Migration?

As many as you like. As long as a model supports skills, you can use Extension Migration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Extension Migration AI skill free?

Yes. It is published on GitHub by quangpl under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇