---
name: chrome-extension-idea-generator
description: "Turns a pain point into a shortlist of Chrome extension concepts worth building, each with its core features, who pays for it, the permissions it needs, and an honest build estimate. Use when someone wants Chrome extension ideas for a specific problem or niche, ranked with features, monetisation, permissions, and build effort. Do not use for writing the extension code or manifest, or brainstorming web apps and mobile apps. Related topics: coding, product, chrome."
---

# Chrome Extension Idea Generator

Turns a pain point into a shortlist of Chrome extension concepts worth building, each with its core features, who pays for it, the permissions it needs, and an honest build estimate.

## When to use

Use this skill when someone wants Chrome extension ideas for a specific problem or niche, ranked with features, monetisation, permissions, and build effort. Do not use it for writing the extension code or manifest, or brainstorming web apps and mobile apps.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Identify the exact page or moment where the pain occurs and discard any concept that a bookmarklet, site setting, or existing tool already covers.
3. Draft the requested number of concepts, each with a name, a one-sentence pitch, and the selected detail fields filled in.
4. List the Manifest V3 permissions each concept needs and flag any that require broad host access, since that slows review and adoption.
5. Assign a monetisation model and a build-complexity rating with the hardest part named, for every idea.
6. Rank the ideas by value to the user divided by effort and name the one to build first.

## Inputs

- **Problem to solve or niche** (longer free text)
- **Target user** (free text, e.g. "developers or recruiters or online sellers")
- **Competing solutions** (longer free text)
- **Preferred extension type** (choose any: Productivity tool, Content blocker or modifier, Data extractor, Automation tool, Visual customiser, Service integration, Research assistant)
- **Number of ideas** (number from 3 to 10)
- **Detail to include per idea** (choose any: Core feature list, Target audience, Monetisation model, Technical approach, Permissions required, Estimated build complexity)

## Output

A numbered list of concepts, each with name, pitch, the chosen detail fields, permissions, monetisation, and complexity, followed by a ranked table and a one-paragraph pick for the first build.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Chrome Extension Idea Generator

Generate Chrome extension concepts for this problem and rank them by how worth building they are.

- Problem to solve or niche: {{Problem to solve or niche}}
- Target user: {{Target user}}
- Competing solutions: {{Competing solutions}}
- Preferred extension type: {{Preferred extension type}}
- Number of ideas: {{Number of ideas}}
- Detail to include per idea: {{Detail to include per idea}}

Start from the moment the pain occurs: an extension earns its place only when the user is already on the page, so prefer ideas that act on the current tab over ideas that are really a web app with an icon. Discard concepts that a bookmarklet or a site setting already solves. For each idea that survives, give a working name, a one-sentence pitch, the selected detail fields, and the Manifest V3 permissions it would need, since broad host permissions slow store review and scare users. For the monetisation model, pick between free, one-time, subscription, or a lead-in to a paid service, and say which one fits the user's willingness to pay. Rate build complexity as weekend, two weeks, or a month or more, naming the hardest part. Close with a ranking of the ideas by value to the user divided by effort, and name the one you would build first and why.

## Pitfalls

- Pitching a web app with a toolbar icon; if the idea does not act on the current tab or page, an extension is the wrong form.
- Ignoring permissions, which decide store review time and install conversion more than features do.
- Rating every idea as easy; an extension that touches many sites' DOM breaks whenever those sites redeploy.
