chrome-ext-troubleshooting — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited chrome-ext-troubleshooting (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Common problems fall into three categories: build/packaging issues, runtime bugs, and Chrome Web Store rejections. Most have straightforward diagnoses once the pattern is recognized.
Windows is case-insensitive; CWS reviewer runs on Linux (case-sensitive). Background.js works locally but fails on submission (Yellow Magnesium rejection).
Fix: Verify all file paths match exactly, including capitalization. Test on a case-sensitive filesystem or review the packed .zip contents.
Content scripts cannot load extension assets (images, fonts, CSS) without declaring them:
{
"web_accessible_resources": [{
"resources": ["images/*", "fonts/*"],
"matches": ["<all_urls>"]
}]
}Third-party libraries may internally use eval(), violating MV3 CSP. Audit dependencies:
# Search for eval in bundled output
grep -r "eval(" .output/chrome-mv3/
grep -r "new Function(" .output/chrome-mv3/Fix: Replace the library, isolate in a sandbox page, or find an alternative.
Firefox requires a sources .zip that can rebuild the extension. .env files or secrets may leak:
Fix: Add .env*, *.pem, and credentials to .gitignore and verify they're excluded from the ZIP.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Event not firing after restart | Listener inside async function | Move to top level, register synchronously |
| State lost between events | Global variables in service worker | Use chrome.storage |
| Timer not executing | setTimeout in service worker | Replace with chrome.alarms |
Message response is null | Missing return true in async listener | Add return true |
| Content script not injecting | Missing matches or permissions | Check manifest and host permissions |
| Fetch failing in service worker | Using XMLHttpRequest | Replace with fetch() |
| Storage writes silently failing | Sync quota exceeded | Check quotas, batch writes |
| Popup state disappears | Relying on React state only | Back with chrome.storage |
| Code | Name | Common Cause | Quick Fix |
|---|---|---|---|
| Blue Argon | Remote Code | eval(), CDN scripts, dynamic imports | Bundle all deps locally |
| Yellow Magnesium | Packaging | Wrong file paths, missing files | Test packed .zip on Linux |
| Yellow Zinc | Metadata | Bad description, missing icons | Provide all required assets |
| Purple Potassium | Excessive Permissions | Over-requesting permissions | Audit with activeTab, optional perms |
| Purple Lithium | Privacy | Missing privacy policy | Add accessible privacy policy URL |
| Purple Copper | Data Security | HTTP, data in URL params | Use HTTPS everywhere |
| Red Family | Single Purpose | Bundled unrelated features | Split into separate extensions |
| Red Titanium | Obfuscation | Non-standard minification | Use standard minifiers only |
| Grey Titanium | Affiliates | Hidden affiliate injection | Disclose and require user action |
Before every Chrome Web Store submission:
<all_urls> audit)optional_permissionseval(), new Function(), setTimeout(string) in codebase or dependencies.zip tested locally (not just unpacked).env or credentials in package~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.