Audit Chrome extensions against Chrome Web Store Featured-badge and Established Publisher badge criteria, producing a prioritized fix plan to qualify.
A Claude Code plugin that audits your Chrome extension against the Chrome Web Store Featured badge and Established Publisher badge criteria, then produces a prioritized fix plan to qualify.
The Featured badge is a human review by the Chrome Web Store team — there's no application queue you can pay or fast-track your way through. The only lever is genuinely meeting Google's published bar. This skill tells you exactly where you stand and what to fix first.
Featured extensions get preferential placement in Chrome Web Store search and collections — for most extensions it's the single biggest discoverability lever available. But the criteria are scattered across support pages, developer docs, and best-practice guides, and a listing that looks fine can still be silently disqualified by a stale privacy policy, an over-broad permission, or a screenshot that doesn't show the extension in use.
Built from Google's published criteria:
Badges can't be bought — the skill never suggests gaming tactics (incentivized reviews, keyword stuffing), only genuinely meeting the published bar.
As a Claude Code plugin (recommended):
/plugin marketplace add divyamrastogi/cws-featured-badge-skill
/plugin install cws-featured-badge@divyamrastogi-skills
Or copy the skill directly:
git clone https://github.com/divyamrastogi/cws-featured-badge-skill.git
# personal skills (all projects)
cp -r cws-featured-badge-skill/skills/cws-featured-badge ~/.claude/skills/
# or project-level
cp -r cws-featured-badge-skill/skills/cws-featured-badge .claude/skills/
Open Claude Code in your extension's repo and ask things like:
The skill triggers automatically on Featured-badge, CWS-badge, and listing-quality questions.
.claude-plugin/
├── plugin.json # plugin metadata
└── marketplace.json # makes this repo installable as a marketplace
skills/
└── cws-featured-badge/
├── SKILL.md # workflow + report format
└── references/
├── badge-criteria.md # Google's criteria, verbatim, with sources
└── audit-checklist.md # the 7-area, evidence-based checklist
If this plugin helped your extension get featured, you can support my work:
The plugin is pure Markdown instructions — no telemetry, no servers, no data collection. Full policy: javascriptbit.com/cws-featured-badge/privacy
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub divyamrastogi/cws-featured-badge-skill --plugin cws-featured-badgeDiagnose and fix Claude in Chrome MCP extension connectivity issues
Keep your coding agent up to date with the latest web best practices
Evaluates code against Apple's App Store Review Guidelines for iOS, macOS, tvOS, watchOS, and visionOS apps
Use this agent when preparing app store listings, researching keywords, optimizing app metadata, improving conversion rates, or analyzing app store performance. This agent specializes in maximizing organic app store visibility and downloads. Examples:\n\n<example>\nContext: Preparing for app launch
This command provides the context necessary for Claude Code to create the Desktop Extension or .dxt file of an MCP.
Ultra-compressed communication mode. Cuts 65% of output tokens (measured) while keeping full technical accuracy by speaking like a caveman.