nex-meeting-finder
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.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
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.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "nex-meeting-finder". What can I use from this package immediately?
Expected outcome:
- 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.
Using "nex-meeting-finder". Outline the documented architecture and the evidence needed before deployment.
Expected outcome:
- 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.
Security Audit
SafeAll 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.
Risk Factors
โ๏ธ External commands (6)
๐ Network access (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/nexaiguy-nex-meeting-finder/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/nexaiguy-nex-meeting-finder?utm_source=security_passport_badge)HTML badge
<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>Embed card
<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>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
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 citation
@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 Score
Why this score Evidence Confidence: MediumWhat You Can Build
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.
Try These Prompts
Summarize the meeting-finder concept and its limitations. Clearly distinguish documented features from code actually included in this package.
Outline the documented Manifest V3 architecture and intended file responsibilities. Identify missing implementation materials without claiming to inspect absent files.
Create an implementation plan for Zoom and Google Meet link detection with Join buttons. Include dynamic-page updates, duplicate prevention, and minimal permissions.
Create a security and behavior validation checklist for a future implementation. Cover permissions, hostile page content, link validation, local storage, and layout regressions.
Best Practices
- 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.
Avoid
- 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.