Not in the top 1,000 by GitHub stars

divyamrastogi/cws-featured-badge-skill

Claude Code skill that audits Chrome extensions against Chrome Web Store Featured/Established Publisher badge criteria

History

Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.

View weekly changes

skills/cws-featured-badge/SKILL.md

Week of Nov 2, 2026 · +0 / −0 lines

Before Network or broad shell → After Network or broad shell

7deed08c6c20 → 7deed08c6c20

Compare on GitHub

Week of Oct 26, 2026 · Line counts unavailable

Before Not checked yet → After Network or broad shell

First observation → 7deed08c6c20

No earlier version was observed for comparison.

Compare on GitHub

View on GitHubAdd to my skills

Verified commit 7deed08c6c2086dd141d8e6c30711101f0261651

git clone --filter=blob:none --no-checkout https://github.com/divyamrastogi/cws-featured-badge-skill.git .hotskills/divyamrastogi-cws-featured-badge-skill && git -C .hotskills/divyamrastogi-cws-featured-badge-skill checkout --detach 7deed08c6c2086dd141d8e6c30711101f0261651 # Copy each selected skill directory from .hotskills/divyamrastogi-cws-featured-badge-skill into .claude/skills/<skill-name>/
14GitHub stars
0stars in 7 days
1skill in this repository
0commits in 30 days

Heat

0.3
  • Star growth, last 7 daysNot available
  • Star growth, last 24 hoursNot available
  • Rank movement, last 7 daysNot available
  • Commits, last 30 daysNot available
  • Accounts asking about it through MCP, last 7 daysNot available
  • Hot votes this weekNot available

Heat never changes the order by stars, and sponsorship never touches it. How heat works

Stars over time

Oct 25, 2026Oct 25, 202614

30-day change not yet available: not enough history.

Individual skills in this repository

How it works

cws-featured-badge

When your agent uses it

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.

What it loads into context

Frontmatter

115 tokens

Always available to the agent

SKILL.md

1,146 tokens

When the skill is activated

Reference documents

2,375 tokens

Loaded on request

Token counts are estimates. Scripts run separately; they are not counted as reference context.

The playbook

  1. Workflow
  2. Judgment calls

Files

  • ../../.claude-plugin/marketplace.jsonasset716 bytes
  • ../../.claude-plugin/plugin.jsonasset689 bytes
  • SKILL.mdcore5,241 bytes
  • SKILL.mdcore5,241 bytes
  • references/audit-checklist.mddoc5,716 bytes
  • references/badge-criteria.mddoc4,676 bytes
Read SKILL.md

# 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"
View the complete source on GitHub

Skills included

  • cws-featured-badge

Repository facts

License
MIT
Created
Jun 11, 2026
Last pushed
Jul 8, 2026
Forks
1
Open issues
0
Project activity
Slowing

Before you install

Network or broad shell

Automated signals, not a guarantee

Checked Nov 5, 2026

Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.

Show 1 note
  • skills/cws-featured-badge/SKILL.md:1 Analysis incomplete: Referenced executable target unavailable; not analyzed
Show all 16 signals by file

.claude-plugin/marketplace.json

  • Network accessline 4
    "owner": {     "name": "Divyam Rastogi",     "url": "https://github.com/divyamrastogi"
  • Network accessline 5
    "name": "Divyam Rastogi",     "url": "https://github.com/divyamrastogi"   },
  • Network accessline 6
    "url": "https://github.com/divyamrastogi"

.claude-plugin/plugin.json

  • Network accessline 6
    "author": {     "name": "Divyam Rastogi",     "url": "https://github.com/divyamrastogi"
  • Network accessline 7
    "name": "Divyam Rastogi",     "url": "https://github.com/divyamrastogi"   },
  • Network accessline 8
    "url": "https://github.com/divyamrastogi"
  • Network accessline 9
    },   "homepage": "https://javascriptbit.com/cws-featured-badge/",   "repository": "https://github.com/divyamrastogi/cws-featured-badge-skill",
  • Network accessline 10
    "homepage": "https://javascriptbit.com/cws-featured-badge/",
  • Network accessline 11
    "repository": "https://github.com/divyamrastogi/cws-featured-badge-skill",

skills/cws-featured-badge/references/audit-checklist.md

  • Network accessline 22
    | Item | How to verify | |---|---| | B1. All network calls over HTTPS | grep for `http://` in fetch/XHR/WebSocket URLs (localhost in test code is fine) |
  • Network accessline 23
    |---|---| | B1. All network calls over HTTPS | grep for `http://` in fetch/XHR/WebSocket URLs (localhost in test code is fine) | | B2. No remote code execution | No `eval` of fetched strings, no remotely-loaded scripts (MV3 also enforces th
  • Network accessline 24
    | B1. All network calls over HTTPS | grep for `http://` in fetch/XHR/WebSocket URLs (localhost in test code is fine) |

skills/cws-featured-badge/references/badge-criteria.md

  • Network accessline 6
    - Badges overview: https://support.google.com/chrome_webstore/answer/1050673 (see the "Understand Chrome Web Store badges" section)
  • Network accessline 7
    - Discovery & featuring: https://developer.chrome.com/docs/webstore/discovery
  • Network accessline 8
    - Best practices: https://developer.chrome.com/docs/webstore/best-practices
  • Network accessline 9
    - Program policies: https://developer.chrome.com/docs/webstore/program-policies

How the signals fit together

Facts from a static read of the files at the pinned commit. They describe what the code does, not why.

Some files could not be read; the facts below still hold.

Signal confidence: 7 facts

Works with

Agent compatibility, from the files in this repository
AgentStatusEvidenceInstall to
Claude CodeNativeManifest .claude-plugin/marketplace.json.claude/skills/<skill-name>/
CodexCompatibleStandard SKILL.md skills/cws-featured-badge/SKILL.md.agents/skills/<skill-name>/
CursorCompatibleStandard SKILL.md skills/cws-featured-badge/SKILL.md.cursor/skills/<skill-name>/
Gemini CLICompatibleStandard SKILL.md skills/cws-featured-badge/SKILL.md.gemini/skills/<skill-name>/
GitHub CopilotCompatibleStandard SKILL.md skills/cws-featured-badge/SKILL.md.github/skills/<skill-name>/
OpenCodeCompatibleStandard SKILL.md skills/cws-featured-badge/SKILL.md.opencode/skills/<skill-name>/
  • Native The repository ships a manifest, folder or frontmatter field for this agent.
  • Compatible A standard SKILL.md that this agent can read.
  • Unknown No evidence either way.

Derived automatically from paths, manifests and frontmatter. Not tested on each agent.