スキル nex-color-spy-ext
📦
nex-color-spy-ext
v1.2 コンテンツリビジョン r1 安全 🌐 ネットワークアクセス
Plan a Chrome CSS Inspector Extension
Planning a browser CSS inspector requires decisions about overlay isolation, inspection metrics, and extension architecture. This guide outlines those decisions without supplying executable extension source.
対応: Claude Codex Code(CC)
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
Review the Skillstore skill "nex-color-spy-ext" from https://skillstore.io/skills/nexaiguy-nex-color-spy-ext.md and its manifest at https://skillstore.io/api/skills/nexaiguy-nex-color-spy-ext/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「nex-color-spy-ext」を使用しています。 What is actually included, and can I load it into Chrome?
期待される結果:
- The package contains a public Markdown guide.
- Extension scripts, source files, and templates are not included.
- You need a separate implementation before using Chrome's Load unpacked option.
「nex-color-spy-ext」を使用しています。 Summarize the inspector requirements for our prototype.
期待される結果:
- Use Manifest V3 and a Shadow DOM overlay.
- Inspect element colors, font families, font sizes, margins, padding, and dimensions.
- Plan clipboard copying, a keyboard toggle, and persistent settings.
- Account for protected browser pages and unsupported canvas or SVG internals.
- These are documented requirements, not verified implementation results.
セキュリティ監査
安全v1 • 2026/11/2 バージョン別レポートを開く
All five static findings are false positives: attribution links and ordinary extension-development prose do not establish network execution or system reconnaissance. No evidence found of prompt injection, credential access, or data exfiltration in the reviewed guide. Extension source is explicitly absent, so its runtime security cannot be assessed.
1
スキャンされたファイル
97
解析済み行数
0
レビュー項目
0
誤検知を無視
リスク要因
🌐 ネットワークアクセス (3)
最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。
監査者: codex
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/nexaiguy-nex-color-spy-ext/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/nexaiguy-nex-color-spy-ext?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/nexaiguy-nex-color-spy-ext?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/nexaiguy-nex-color-spy-ext/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/nexaiguy-nex-color-spy-ext.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形式の引用
nexaiguy. (2026). nex-color-spy-ext security audit report (audit version 1) [Author version 1.2]. Skillstore. https://skillstore.io/skills/nexaiguy-nex-color-spy-ext/audits/1BibTeX形式の引用
@techreport{nexaiguy-nexaiguy-nex-color-spy-ext-2026,
author = {nexaiguy},
title = {nex-color-spy-ext security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/nexaiguy-nex-color-spy-ext/audits/1},
note = {Author version 1.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nex-color-spy-ext security audit report (audit version 1)"
version: "1.2"
type: report
authors:
- name: "nexaiguy"
date-released: "2026-11-02"
url: "https://skillstore.io/skills/nexaiguy-nex-color-spy-ext/audits/1"
identifiers:
- type: other
value: "skillstore:nexaiguy-nex-color-spy-ext:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中 55
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
83
仕様準拠
作成できるもの
Plan an inspector prototype
Translate the documented overlay, metrics, and toggle features into requirements for a new Chrome extension.
Define design inspection needs
List the typography, spacing, and color values a proposed inspection tool should expose.
Study extension development
Use the guide to discuss Manifest V3, Shadow DOM isolation, and unpacked loading before implementing an extension.
これらのプロンプトを試す
Understand the guide
Summarize the inspector described in this guide. Separate documented features from files actually included, and explain what is missing.
Define inspection requirements
Create a requirements checklist for a CSS inspector covering colors, fonts, spacing, dimensions, clipboard copying, and keyboard toggling. Include the documented limitations.
Plan the extension architecture
Propose a Manifest V3 architecture for the described inspector using vanilla JavaScript and Shadow DOM. Label implementation proposals separately from documented facts.
Design a verification plan
Develop a verification plan for a future implementation covering permissions, clipboard actions, settings persistence, overlay isolation, and protected pages. Do not claim tests passed.
ベストプラクティス
- Confirm that extension source is available before planning installation or packaging.
- Treat advertised features as requirements until an implementation and its permissions have been reviewed.
- Test any future implementation on ordinary pages, complex layouts, and browser-protected pages.
回避
- Assuming the guide includes a working extension or executable templates.
- Claiming Chrome Web Store approval, runtime safety, or successful tests without implementation evidence.
- Expecting the documented inspector to inspect canvas internals or bypass browser page restrictions.
よくある質問
Does this package include a working Chrome extension?
No. The public guide explicitly states that scripts, extension source, and templates are not included.
Which CSS values does the guide describe?
It describes colors, font families, font sizes, margins, padding, and element dimensions.
Does the documented architecture need a build tool?
No. It describes vanilla JavaScript, HTML, and CSS without Webpack, Vite, or NPM build steps.
Why does the guide recommend Shadow DOM?
Shadow DOM separates the inspector interface from host page styles. The guide does not include an implementation to verify.
How would I install a separate implementation?
After obtaining and reviewing source files, open Chrome's extensions page, enable Developer mode, and select the folder with Load unpacked.
Can the described tool inspect every page element?
No. The guide excludes canvas and SVG internals and notes limited inspection on browser-protected pages.