Menu

Individual skill

cws-featured-badge

0upvotes

Audit any Chrome extension against Chrome Web Store Featured-badge and Established Publisher badge criteria, and produce a prioritized fix plan to qualify. Use this whenever the user mentions the Chrome Web Store Featured badge, getting an extension featured, CWS badges, store listing quality review, badge readiness, extension discoverability, or asks "is my extension ready for the Web Store" — even if they don't say the word "badge". Also use it before any Chrome Web Store submission or major listing update to catch disqualifying issues early.

skills/cws-featured-badge/SKILL.md

Read pinned source

Source commit 7deed08c6c2086dd141d8e6c30711101f0261651

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
14
Repository last updated
Jul 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Chrome Web Store Featured Badge Audit

Audit a Chrome extension codebase + store listing against Google's published
criteria for the **Featured badge** (manually reviewed by the CWS team) and the
**Established Publisher badge** (granted on publisher standing), then produce a
report with a prioritized fix plan.

Two facts shape every audit:
1. **Badges cannot be bought or expedited.** The only lever is genuinely meeting
   the criteria. Never suggest gaming tactics (incentivized reviews, keyword
   stuffing); these violate program policies and disqualify the extension.
2. **Featured is a human review.** The reviewer checks best-practice adherence,
   UX quality, modern platform APIs, privacy respect, and listing quality. The
   audit must therefore judge *quality*, not just tick boxes — "has screenshots"
Back to top