スキル chrome-extensions

📦

chrome-extensions

Name: chrome-extensions
Author: googlechrome

コンテンツリビジョン r1 高リスク ⚙️ 外部コマンド🌐 ネットワークアクセス🔑 環境変数⚡ スクリプトを含む📁 ファイルシステムへのアクセス

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.

対応: Claude Codex Code(CC)

⚠️ 38 不十分

Maintain this Skill? Claim it ⚠️ 38 不十分

インストール前に停止して確認を求めてください。

計画を確認し、ファイルを変更する前にユーザーの明示的な同意を得てください。

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

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.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/googlechrome-chrome-extensions.md 署名済み manifest GET /api/skills/googlechrome-chrome-extensions/manifest 署名済み lockfile GET /api/skills/googlechrome-chrome-extensions/lockfile

テストする

「chrome-extensions」を使用しています。 My side panel does not open when I click the extension icon.

期待される結果:

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.

「chrome-extensions」を使用しています。 Prepare my local reading-list extension for the Chrome Web Store.

期待される結果:

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.

セキュリティ監査

高リスク

v1 • 2026/10/21 バージョン別レポートを開く

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.

スキャンされたファイル

3,543

解析済み行数

レビュー項目

誤検知を無視

確認済みのセキュリティ上の懸念 (1)

高

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.

リスク要因

⚙️ 外部コマンド (50)

🌐 ネットワークアクセス (38)

🔑 環境変数 (1)

references/extensions/api-calling.md:66

⚡ スクリプトを含む (24)

📁 ファイルシステムへのアクセス (4)

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

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

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

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)

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>

埋め込みカード

<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>

学術引用 (APA · BibTeX · CFF)

APA形式の引用

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

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"

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

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.

これらのプロンプトを試す

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.

ベストプラクティス

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.

回避

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.

よくある質問

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.