chrome-extension
Skill1 starsChanged 4 months agoMITView on GitHub
Build and publish Chrome extensions. Covers Manifest V3 scaffold, popup-only architecture, icon generation, and Chrome Web Store submission with every required form field pre-filled. Use when asked to build a Chrome extension, publish to the Chrome Web Store, create a browser extension, or set up a Manifest V3 project. Also use when troubleshooting Chrome extension rejections or preparing store listing assets.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- samber/cc-skillstheir own version, first seen Nov 1, 2026
- JCodesMore/ai-chrome-extension-templatetheir own version, first seen Jul 12, 2026
- human-pages-ai/ai-skillstheir own version, first seen Apr 13, 2026
- hssh8917/cc-skillstheir own version, first seen Apr 10, 2026
- kevinaimonster/skill-hubtheir own version, first seen Mar 18, 2026
- Governs-AI/ConvoPorttheir own version, first seen Mar 6, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- samber/cc-skills★ 242same name
- JCodesMore/ai-chrome-extension-template★ 10same name
- kevinaimonster/skill-hub★ 4same name
- Governs-AI/ConvoPort★ 2same name
- hssh8917/cc-skills★ 2same name
- human-pages-ai/ai-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- abmSkill
- agent-teamSkill
- analyticsSkill
- automationSkill
- blog-auditSkill
- blog-postSkill
- brandingSkill
- briefSkill
- business-acquisitionSkill
- business-hacksSkill
- claude-code-auditSkill
- closingSkill
- cold-outreachSkill
- communitySkill
- content-ideaSkill
- content-planSkill
- contentSkill
- croSkill
- customer-successSkill
- emailSkill
- entrepreneurSkill
- fact-checkSkill
- financeSkill
- fundraisingSkill
- ghlSkill
- growthSkill
- gtmSkill
- handoffSkill
- hooksSkill
- humanize-strip-aiSkill
- leadsSkill
- local-seoSkill
- manualSkill
- marketing-hacksSkill
- n8nSkill
- nurtureSkill
- offerSkill
- optimize-vs-skillSkill
- paid-mediaSkill
- partnershipsSkill
- personal-brandSkill
- portable-promptSkill
- product-marketingSkill
- productSkill
- prSkill
- replit-qualitySkill
- researchSkill
- sales-managementSkill
- save-sessionSkill
- scalingSkill
- seo-hacksSkill
- seoSkill
- social-postSkill
- technical-auditSkill
- tone-of-voiceSkill
- ui-ux-auditSkill
- uxSkill
- vibe-codingSkill
- web-designSkill
- youtube-seoSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 14 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
If $ARGUMENTS describes what the extension should do: build it end-to-end and prepare all store submission materials.
- Distinctive: line 17
If $ARGUMENTS mentions a rejection or review issue: diagnose and fix.
- Distinctive: line 18
If no arguments: ask what the extension should do and what website it should link back to (if any).
- Distinctive: line 40
No subdirectories. No nested folders.
- Distinctive: line 77
Only add content scripts if the extension must modify or read pages on other websites.
- Distinctive: line 79
Add content scripts in V2 update after approval
- Distinctive: line 102
Use the brand colour as background
- Distinctive: line 104
Must be recognisable at 16px (keep it simple)
- Very specific: line 143
All external links use target="_blank" rel="noopener"
- Distinctive: line 144
Keep all links to a single domain (consistent, trustworthy)
- Distinctive: line 218
Use a free privacy policy generator
- Very specific: line 248
Create manifest.json with popup-only architecture
- Very specific: line 251
Test: chrome://extensions → Developer mode → Load unpacked
- Distinctive: line 252
Verify all links open correct URLs
- Distinctive: line 253
Create a zip of the folder (exclude .DS_Store, .git, etc.)
- Distinctive: line 263
When building an extension, deliver:
- Distinctive: line 264
All source files ready to load as unpacked extension
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Chrome Extension Skill
You are building a Chrome extension optimised for fast Chrome Web Store approval. The default architecture is popup-only with zero permissions, which Google approves quickly with minimal review friction.
When invoked
If $ARGUMENTS describes what the extension should do: build it end-to-end and prepare all store submission materials. If $ARGUMENTS mentions a rejection or review issue: diagnose and fix. If no arguments: ask what the extension should do and what website it should link back to (if any).
Approved Architecture (Popup-Only)
This is the pattern Google has approved without friction. Use this as the default unless the extension genuinely requires content scripts.
File Structure (flat, all files in root)
extension-name/
├── manifest.json
├── popup.html
├── popup.css
├── popup.js
├── [additional .js files as needed]
├── [data files like .json]
├── icon16.png
├── icon48.png
└── icon128.pngNo subdirectories. No nested folders. Everything in the root.
manifest.json Template
{
"manifest_version": 3,
"name": "Extension Name",
"version": "1.0",
"description": "Under 132 characters. Be specific. Include a number if possible.",
"homepage_url": "https://your-website.com/",
"action": {
"default_popup": "popup.html",
"default_icon": {
"16": "icon16.png",
"48": "icon48.png",
"128": "icon128.png"
}
},
"icons": {
"16": "icon16.png",
"48": "icon48.png",
"128": "icon128.png"
},
"permissions": []
}Key rules:
manifest_versionmust be 3 (V2 is deprecated)descriptionmax 132 characterspermissions: [](empty array, zero permissions = fastest approval)homepage_urlis where the Chrome Web Store links to (your backlink)- No
host_permissions, nocontent_scripts, noweb_accessible_resourcesfor V1 - No
backgroundservice worker unless needed
When Content Scripts Are Needed
Only add content scripts if the extension must modify or read pages on other websites. This triggers stricter review. If you need them:
- Ship V1 as popup-only first to get the extension live
- Add content scripts in V2 update after approval
- Content scripts require
host_permissionsfor each target domain - You will need a privacy policy explaining what data you access and why
Icons
Three sizes required: 16px, 48px, 128px. All PNG format.
Starting scaffold for generating them in Python if no design tool is available. Complete the draw and PNG-write steps yourself:
import struct, zlib, math
def create_icon(size, letter, bg_color_hex, filename):
# bg_color_hex like "#3366CC"
r = int(bg_color_hex[1:3], 16)
g = int(bg_color_hex[3:5], 16)
b = int(bg_color_hex[5:7], 16)
# ... generate circle with letterIcon guidelines:
- Use the brand colour as background
- White letter or simple symbol on coloured circle
- Must be recognisable at 16px (keep it simple)
- 128px version is also used as the store icon
Popup Pattern
popup.html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Extension Name</title>
<link rel="stylesheet" href="popup.css">
</head>
<body>
<div class="container">
<!-- Main UI here -->
<!-- CTA (optional, soft) -->
<div class="cta">
<p>Need help?</p>
<a href="https://your-website.com/contact/" target="_blank" rel="noopener">Get in touch</a>
</div>
<!-- Footer with backlink -->
<div class="footer">
<a href="https://your-website.com" target="_blank" rel="noopener">Powered by Your Brand</a>
</div>
</div>
<script src="popup.js"></script>
</body>
</html>Rules:
- All external links use
target="_blank" rel="noopener" - Keep all links to a single domain (consistent, trustworthy)
- Width: 340-450px is standard for popup
- Load data files with
fetch(chrome.runtime.getURL('data.json'))
Chrome Web Store Submission
Required Form Fields
| Field | What to Put |
| Title | Pulled from manifest name. Max 75 chars. |
| Summary | Pulled from manifest description. Max 132 chars. |
| Description | Up to 16,000 chars. See template below. |
| Category | Usually "Tools". Other options: "Productivity", "Fun", "Search Tools" |
| Language | Match your target audience. Pick your market's locale, e.g. "English" or a country-specific English variant. |
Description Template
[Extension Name] gives you [one-line value prop].
[How to use it — 2-3 sentences explaining the interaction]
Features:
- [Feature 1]
- [Feature 2]
- [Feature 3]
Useful for:
- [Use case 1]
- [Use case 2]
- [Use case 3]
No data is collected. No account required. Works entirely offline after installation.
Built by [Brand Name] ([website URL]).Graphic Assets
| Asset | Size | Format | Required? |
| Store icon | 128x128 | PNG | Yes (use icon128.png) |
| Screenshots | 1280x800 or 640x400 | JPEG or 24-bit PNG (no alpha) | Yes, at least 1 (max 5) |
| Small promo tile | 440x280 | JPEG or 24-bit PNG (no alpha) | No |
| Marquee promo tile | 1400x560 | JPEG or 24-bit PNG (no alpha) | No |
| Promo video | YouTube URL | N/A | No |
Screenshots: Load the extension in Chrome, click it, take a screenshot of the popup in use with results showing. Resize to 1280x800 or 640x400. Must be JPEG or 24-bit PNG with no alpha channel.
URLs
| Field | What to Put |
| Official URL | Select from Google Search Console if verified, otherwise "None" |
| Homepage URL | Your website URL (this is the backlink) |
| Support URL | Your website contact page URL |
Privacy and Permissions
| Field | Value |
| Single purpose description | "[Extension name] lets users [one action]. [How it works in one sentence]. All data is bundled locally. No user data is collected, stored, or transmitted." |
| Are you using remote code? | "No" (unless you load external JS/Wasm) |
| Permission justification | Leave blank if no permissions and no remote code |
| Data usage checkboxes | All unchecked (for popup-only with no data collection) |
| Three certifications | Check all three (no data sold, no unrelated use, no creditworthiness) |
| Mature content | No (unchecked) |
Privacy Policy
Google requires a privacy policy URL. Options:
- Host a simple privacy policy page on your website (another backlink)
- Use a free privacy policy generator
- Content: state the extension collects no data, makes no network requests, stores nothing
Backlink Opportunities
A Chrome extension can generate up to 4 backlinks:
homepage_urlin manifest (shows on Chrome Web Store listing page)- Homepage URL in store submission form
- Privacy policy page hosted on your website
- CTA and footer links inside the popup (not crawled by Google, but user-facing)
Common Rejection Reasons
- Too many permissions — Request only what you use. Zero permissions = no friction.
- Missing single purpose — Google wants a clear, narrow purpose. One thing, stated simply.
- Description mismatch — What the description says must match what the extension does.
- Missing privacy policy — Required even if you collect nothing.
- Content scripts on broad domains — Avoid
*://*/*matches. Be specific. - Remote code — Loading JS from external URLs gets flagged. Bundle everything locally.
- Deceptive install tactics — CTA text, screenshots, and description must match actual functionality.
Build Workflow
- Define what the extension does (one purpose)
- Create manifest.json with popup-only architecture
- Build popup HTML/CSS/JS
- Generate icons (16, 48, 128px)
- Test:
chrome://extensions→ Developer mode → Load unpacked - Verify all links open correct URLs
- Create a zip of the folder (exclude .DS_Store, .git, etc.)
- Submit to Chrome Web Store Developer Dashboard ($5 one-time registration)
- Fill all form fields per the tables above
- Take and upload at least 1 screenshot
- Submit for review (typically 1-3 business days)
Output Format
When building an extension, deliver:
- All source files ready to load as unpacked extension
- A pre-filled table of every Chrome Web Store form field
- A description block ready to paste
- A single purpose description ready to paste
- Instructions for taking screenshots and submitting
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

