Chrome Extension Idea Generator skill for Claude and Codex
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…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
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.
What it will ask you for
- 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)
How it works
- Identify the exact page or moment where the pain occurs and discard any concept that a bookmarklet, site setting, or existing tool already covers.
- Draft the requested number of concepts, each with a name, a one-sentence pitch, and the selected detail fields filled in.
- List the Manifest V3 permissions each concept needs and flag any that require broad host access, since that slows review and adoption.
- Assign a monetisation model and a build-complexity rating with the hardest part named, for every idea.
- Rank the ideas by value to the user divided by effort and name the one to build first.
What you get
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.
What it watches out for
- 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.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.