Compétences chrome-extensions

📦

chrome-extensions

Name: chrome-extensions
Author: googlechrome

Révision du contenu r1 Risque élevé ⚙️ Commandes externes🌐 Accès réseau🔑 Variables d’environnement⚡ Contient des scripts📁 Accès au système de fichiers

Build and Prepare Chrome Extensions for Publication

Chrome extension development requires coordinating browser permissions, background behavior, user interfaces, and store requirements. This skill provides Manifest V3 examples and publishing templates to guide implementation and release preparation.

Prend en charge: Claude Codex Code(CC)

⚠️ 38 Médiocre

Maintain this Skill? Claim it ⚠️ 38 Médiocre

Arrêtez-vous et demandez confirmation avant l’installation.

Examinez le plan et obtenez le consentement explicite de l’utilisateur avant de modifier des fichiers.

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

Review the Skillstore skill "chrome-extensions" from https://skillstore.io/skills/googlechrome-chrome-extensions.md and its manifest at https://skillstore.io/api/skills/googlechrome-chrome-extensions/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/googlechrome-chrome-extensions.md manifest signé GET /api/skills/googlechrome-chrome-extensions/manifest lockfile signé GET /api/skills/googlechrome-chrome-extensions/lockfile

Tester

Utilisation de « chrome-extensions ». My side panel does not open when I click the extension icon.

Résultat attendu:

Diagnosis: the side panel declaration does not provide an opening trigger.
Recommended change: configure action-click opening and remove any conflicting default popup.
Verification: reload the unpacked extension, click its toolbar icon, and check the service worker console.

Utilisation de « chrome-extensions ». Prepare my local reading-list extension for the Chrome Web Store.

Résultat attendu:

Listing draft: Save selected links to a reading list stored on your device.
Permission justification: storage retains saved links; contextMenus provides the save action.
Release checks: verify actual data handling, prepare current screenshots, and inspect the final package for secrets and development files.

Audit de sécurité

Risque élevé

v1 • 21/10/2026 Ouvrir le rapport versionné

All 265 static matches concern documented development examples, prohibited patterns, or defensive packaging instructions rather than the risks alleged by their detectors. No evidence found of credential exfiltration, covert capture uploads, or audit-directed prompt injection. One semantic finding identifies incorrect playground-isolation guidance that could encourage unsafe handling of untrusted HTML and JavaScript.

Fichiers analysés

3,543

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Préoccupations de sécurité confirmées (1)

Élevé

references/extensions/csp-sandbox.md:111-151 SKILL.md:73-78

Unsafe Isolation Guidance for Untrusted Playground Content

The guide claims, "Both blob URLs and srcdoc create a separate origin, so they bypass the extension's CSP." Blob URLs retain their creator origin, and srcdoc normally inherits its embedding origin; neither example adds explicit iframe sandboxing. Treating these previews as isolated can expose parent DOM data; inherited CSP restrictions do not provide the claimed origin boundary.

The reference explicitly asserts separate-origin isolation, while its Blob and srcdoc examples omit iframe sandboxing. The main skill repeats this recommendation; actual exploitability depends on CSP and surrounding application behavior.

Facteurs de risque

⚙️ Commandes externes (50)

🌐 Accès réseau (38)

🔑 Variables d’environnement (1)

references/extensions/api-calling.md:66

⚡ Contient des scripts (24)

📁 Accès au système de fichiers (4)

references/extensions/icons.md:39 references/extensions/icons.md:59 references/extensions/icons.md:59 references/extensions/icons.md:14

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

https://skillstore.io/skills/googlechrome-chrome-extensions/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/googlechrome-chrome-extensions/security.svg)](https://skillstore.io/skills/googlechrome-chrome-extensions?utm_source=security_passport_badge)

Badge HTML

<a href="https://skillstore.io/skills/googlechrome-chrome-extensions?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/googlechrome-chrome-extensions/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Carte intégrable

<iframe src="https://skillstore.io/embed/skills/googlechrome-chrome-extensions.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citations académiques (APA · BibTeX · CFF)

Citation APA

googlechrome. (2026). chrome-extensions security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/googlechrome-chrome-extensions/audits/1

Citation BibTeX

@techreport{googlechrome-googlechrome-chrome-extensions-2026,
  author = {googlechrome},
  title = {chrome-extensions security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/googlechrome-chrome-extensions/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "chrome-extensions security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "googlechrome"
date-released: "2026-10-21"
url: "https://skillstore.io/skills/googlechrome-chrome-extensions/audits/1"
identifiers:
  - type: other
    value: "skillstore:googlechrome-chrome-extensions:audit:1"
    description: "Skillstore immutable audit report identifier"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

Create a First Extension

Build a Manifest V3 extension with a popup, saved preferences, and content scripts scoped to the required websites.

Debug Extension Integration

Review side panel triggers, service worker state, message responses, and permissions when an existing extension behaves incorrectly.

Prepare a Store Submission

Create a release document covering listing copy, permission explanations, privacy disclosures, required assets, and packaging checks.

Essayez ces prompts

Start a Simple Extension

Build a Manifest V3 extension that saves a theme preference in a popup. Include real icon assets or omit icon references.

Diagnose a Side Panel

Review this extension and fix its side panel opening behavior. Check action configuration, permissions, and message handling, then explain how to verify the changes.

Prepare Publishing Documents

Inspect my extension and draft CHROMEWEBSTORE.md with permission justifications, accurate privacy disclosures, listing copy, and a packaging checklist. Identify missing submission assets.

Review a Script Manager

Review my Manifest V3 script manager for userScripts opt-in, execution worlds, message validation, and update persistence. Verify sandbox boundaries independently and propose focused tests.

Bonnes pratiques

Match every permission and host pattern to an implemented feature, and request the narrowest access that supports it.
Test popup, side panel, messaging, and service worker restart behavior in the supported Chrome versions.
Generate listing claims and privacy disclosures from actual code behavior, then inspect the release package before submission.

Éviter

Copying Blob URL or srcdoc playground examples while assuming they automatically isolate untrusted content.
Requesting broad host access or embedding private API keys without evaluating narrower alternatives.
Claiming that no data leaves the device without checking network calls, analytics, and synchronized storage.

Foire aux questions

Which AI tools can use this skill?

The skill supports Claude, Codex, and Claude Code.

Does it cover Manifest V2?

No. The guidance targets Manifest V3 and directs generated extensions away from Manifest V2 APIs.

Can it help with an existing extension?

Yes. It provides reference patterns for reviewing permissions, side panels, service worker state, messaging, authentication, and other extension features.

Does it publish extensions automatically?

No. It helps prepare documentation and packages, but publication requires your developer account and Chrome Developer Dashboard submission.

Are all security examples ready to copy?

No. The playground isolation guidance needs correction, and all examples require review and testing in your extension context.

Can it write a privacy policy?

It provides templates and guidance based on actual data handling. Review the result against current store requirements and applicable legal obligations.