Back to Skills

store-requirements

verified

Chrome Web Store guidelines and requirements covering Developer Program Policies, single purpose requirement, permission justifications, privacy policy, branding, screenshots, common rejection reasons, and appeal process. Essential for successful store submission.

View on GitHub

Marketplace

fran-marketplace

francanete/fran-marketplace

Plugin

chrome-extension-expert

development

Repository

francanete/fran-marketplace

chrome-extension-expert/skills/store-requirements/SKILL.md

Last Verified

January 20, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/francanete/fran-marketplace/blob/main/chrome-extension-expert/skills/store-requirements/SKILL.md -a claude-code --skill store-requirements

Installation paths:

Claude
.claude/skills/store-requirements/
Powered by add-skill CLI

Instructions

# Chrome Web Store Requirements

## Developer Program Policies

### Core Principles

1. **Single Purpose** - Extension must have one clear purpose
2. **Transparency** - Clearly describe functionality
3. **Privacy** - Respect user data
4. **Security** - No malicious behavior
5. **Quality** - Work as advertised

### Policy Categories

| Category | Key Requirements |
|----------|-----------------|
| Content | No malware, spam, hate, or illegal content |
| Data | Minimal collection, clear disclosure |
| Functionality | Works as described, no deception |
| Monetization | Clear about paid features |
| User Experience | No unwanted behavior |

---

## Single Purpose Requirement

### What It Means

Your extension should do **ONE thing well**, not bundle unrelated features.

**ACCEPTABLE:**
- Tab manager with grouping, search, and organization
- Note-taking with formatting, tags, and sync
- Ad blocker with filter customization

**NOT ACCEPTABLE:**
- Tab manager + weather widget + game
- Coupon finder + screenshot tool
- Anything with "multi-tool" bundled features

### How to Define Purpose

```markdown
## Single Purpose Statement
[Extension Name] helps users [primary action] by [method].

Example:
"TabMaster helps users organize their browser tabs by providing
grouping, search, and session management features."
```

### Feature Justification

All features should relate to the core purpose:

| Feature | Core: Tab Management | Justified? |
|---------|---------------------|------------|
| Tab grouping | Direct | ✅ |
| Tab search | Direct | ✅ |
| Session save | Related | ✅ |
| Tab statistics | Enhancement | ✅ |
| Weather widget | Unrelated | ❌ |
| Ad blocking | Unrelated | ❌ |

---

## Permission Justifications

### When Required

Justifications required for:
- `tabs`
- `webNavigation`
- `history`
- `bookmarks`
- `topSites`
- `browsingData`
- `<all_urls>` or broad host permissions

### Writing Good Justifications

**Structure:**
```
Permission: [permission name]

1. What we use 

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
10094 chars