스킬 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.