Will it change my manifest?

No. It suggests exact before/after changes; you apply them.

Does on-device data really need declaring?

Yes. Google's User Data FAQ says data handled only on the device must still be disclosed, and a privacy policy is required.

Does it guarantee approval?

No. It removes the common causes of rejection; Google's reviewers decide.

Does it work with WXT or Plasmo?

Yes, point it at the built output where manifest.json is generated.

Does it send my code anywhere?

No. Both scripts run locally, read-only, with no network access.

Chrome Web Store Prep From Your Code

Example session with this skill installed

Google rejected my extension for Purple Potassium. Can you fix the permissions and redo the listing? It's a dictionary popup for students reading English websites. The selected word goes to a free dictionary API. No privacy policy yet.

Read your context and instructions
Compiled the chrome web store
Generated the UI component

Fix 5 things first, then it's ready to submit.

Change before submitting

tabs: remove. The code only calls tabs.sendMessage and tabs.query (no url or title filter), and neither needs the permission. This is the likely cause of Purple Potassium.
notifications: remove. No code uses it.
<all_urls> in host_permissions and content_scripts: narrow to https://api.dictionaryapi.dev/*, delete the content_scripts block, and inject content.js from the context-menu click handler with activeTab + scripting.
popup.html:2 loads chart.js from a CDN. That is remote code (Blue Argon, your next rejection). popup.js doesn't use it, so delete the tag.
background.js:12 sends a Google Analytics ping. Remove it, or keep it and declare User activity.

Declared

Website content: the selected word goes to the dictionary API, and your saved lookup history counts too, even though it stays on the device.
User activity: the Analytics ping, plus the local lookup history.

Fill in

{privacy policy URL}. It's required because the extension handles user data.
Screenshots (1280x800), a 128x128 icon and a 440x280 promo tile.

Paste-ready texts are in store-listing/. Re-run me after you change the manifest.

popup.html

TSX · React component

Generated

Example file from a real run - the skill writes it into your workspace.

Connects securely to your tools. The creator never sees your data.

About this skill

Chrome Web Store reviewers compare what you declare with what your code does. Unused permissions, a CDN script, an analytics ping you forgot, or "no data collected" next to a saved history get extensions rejected.

This skill reads your manifest and code first:

Every permission and host pattern: keep / remove / narrow / make optional, with file:line evidence
Paste-ready justifications, single purpose, remote-code answer and all 9 data categories
Catches remote code (Blue Argon) and undeclared data handling before review
Store listing: name, summary, description, screenshot list
A checker for limits, missing justifications and privacy answers that contradict the code

Prepares your submission; Google's reviewers make the final call.

How to use

1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.

Reviews

No reviews yet

Be one of the first to try it. Every listed skill passes our trust checks below.

Security scanned

Passed our 8-point scan before listing

Fresh listing

Recently published to Agensi

Money-back guarantee

Doesn't do what its page promises? You get your money back.

Chrome Web Store Prep From Your Code