スキル nex-meeting-finder
📦
nex-meeting-finder
v1.2 コンテンツリビジョン r1 安全 ⚙️ 外部コマンド🌐 ネットワークアクセス
Plan a Meeting-Link Chrome Extension
Meeting links scattered across web pages can be difficult to locate. This public guide outlines a Chrome extension concept for detecting links and adding Join buttons.
対応: Claude Codex Code(CC)
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
Review the Skillstore skill "nex-meeting-finder" from https://skillstore.io/skills/nexaiguy-nex-meeting-finder.md and its manifest at https://skillstore.io/api/skills/nexaiguy-nex-meeting-finder/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「nex-meeting-finder」を使用しています。 What can I use from this package immediately?
期待される結果:
- Available: a public guide describing the meeting-finder concept, intended architecture, and known limitations.
- Not included: a loadable extension, implementation scripts, or source templates.
- Next step: obtain source code or plan a separate implementation before testing browser behavior.
「nex-meeting-finder」を使用しています。 Outline the documented architecture and the evidence needed before deployment.
期待される結果:
- Architecture: Manifest V3 with content scripts, background workers, popup UI, settings, and local persistence.
- Proposed behavior: detect meeting links, add Join buttons, and extract time context from surrounding text.
- Required evidence: actual source code, permission review, browser testing, and verification of claimed platform coverage.
セキュリティ監査
安全v1 • 2026/11/2 バージョン別レポートを開く
All ten static findings are false positives: Markdown backticks name files, and the URLs provide attribution or catalog references. No evidence found of executable commands, reconnaissance, data exfiltration, or prompt injection in the supplied guide. Extension source is absent, so its security and advertised behavior cannot be verified.
1
スキャンされたファイル
95
解析済み行数
0
レビュー項目
0
誤検知を無視
リスク要因
⚙️ 外部コマンド (6)
🌐 ネットワークアクセス (3)
最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。
監査者: codex
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/nexaiguy-nex-meeting-finder/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/nexaiguy-nex-meeting-finder?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/nexaiguy-nex-meeting-finder?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/nexaiguy-nex-meeting-finder/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/nexaiguy-nex-meeting-finder.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-meeting-finder security audit report (audit version 1) [Author version 1.2]. Skillstore. https://skillstore.io/skills/nexaiguy-nex-meeting-finder/audits/1BibTeX形式の引用
@techreport{nexaiguy-nexaiguy-nex-meeting-finder-2026,
author = {nexaiguy},
title = {nex-meeting-finder security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/nexaiguy-nex-meeting-finder/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-meeting-finder 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-meeting-finder/audits/1"
identifiers:
- type: other
value: "skillstore:nexaiguy-nex-meeting-finder:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中 55
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
83
仕様準拠
作成できるもの
Define an extension implementation plan
Use the documented architecture and file roles to plan a new meeting-link extension without assuming source code is included.
Assess a meeting-link workflow
Review proposed Join buttons, meeting-time context, and local persistence when evaluating a browser-based productivity concept.
Review documentation claims
Separate documented features from missing implementation evidence before requesting source code, permission details, and test results.
これらのプロンプトを試す
Summarize the guide
Summarize the meeting-finder concept and its limitations. Clearly distinguish documented features from code actually included in this package.
Map the architecture
Outline the documented Manifest V3 architecture and intended file responsibilities. Identify missing implementation materials without claiming to inspect absent files.
Plan a focused implementation
Create an implementation plan for Zoom and Google Meet link detection with Join buttons. Include dynamic-page updates, duplicate prevention, and minimal permissions.
Design a validation checklist
Create a security and behavior validation checklist for a future implementation. Cover permissions, hostile page content, link validation, local storage, and layout regressions.
ベストプラクティス
- Confirm that extension source is available before planning installation or deployment.
- Treat the guide as design documentation and verify every implementation claim against actual code.
- Require minimal permissions and tests on static and dynamic pages before deploying any implementation.
回避
- Presenting the documented example response as evidence that source files were generated.
- Assuming production readiness, ten-platform coverage, or browser compatibility without implementation tests.
- Installing unreviewed extension code or granting broad page access solely because the guide recommends the product.
よくある質問
Does this package include a working extension?
No. The supplied package contains only a public guide and explicitly excludes scripts, extension source, and templates.
Which meeting services does the guide mention?
It names Zoom, Google Meet, Microsoft Teams, Webex, and Skype. Its ten-platform support claim cannot be verified without the extension source.
Does the described architecture require build tools?
The guide describes vanilla JavaScript, HTML, and CSS without a build step. No implementation is included to confirm this setup.
Can it synchronize links across devices?
The guide describes client-side operation with local storage and explicitly lists cloud synchronization as unavailable.
Can I use the guide with Claude or Codex?
You can ask Claude, Codex, or Claude Code to summarize the guide and plan development. The guide does not supply runnable extension code.
Can I publish it directly to the Chrome Web Store?
No loadable extension is included. You need implementation files, browser testing, permission review, and compliance checks before submitting an extension.