# 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

```bash
npx skillstore add nexaiguy/nex-meeting-finder
```

## Metadata

- Status: approved
- Slug: nexaiguy-nex-meeting-finder
- Version: 1.2
- Author version: 1.2
- Skillstore revision: r1
- Version status: invalid
- Tree hash: cee7008387ada2472d7a674c923c069f972250e7e011de950c1df81803e8bebf
- Author: nexaiguy
- GitHub username: nexaiguy
- License: MIT
- Repository: https://github.com/nexaiguy/nex-ai-skills/tree/463aaff26593654193deb52f24d18e80ec21e323/skills/nex-meeting-finder
- Ref: 3ddfdca559084abffbfdd188f2ba14b597dcfd9c
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/nexaiguy-nex-meeting-finder
- Manifest: https://skillstore.pages.dev/api/skills/nexaiguy-nex-meeting-finder/manifest

## Capabilities

- Describes meeting-link detection using a MutationObserver for dynamically updated pages.
- Outlines platform-themed badges and Join buttons as intended interface features.
- Describes extracting meeting times from nearby text for popup context.
- Identifies intended manifest, content-script, platform-definition, and popup file roles.
- Explains a proposed zero-build JavaScript, HTML, and CSS architecture.
- Lists client-side operation, no cloud synchronization, and regex detection limitations.

## Use Cases

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

## Prompt Templates

### 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.
```

## Limitations

- The supplied package contains only SKILL.md; extension source, scripts, and templates are absent.
- Link detection, time parsing, platform coverage, and browser compatibility cannot be tested from this package.
- The described architecture has no cloud synchronization and does not target React or Vue builds.
- Production readiness, browser permissions, and Chrome Web Store acceptance are not verified.

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

## Anti Patterns

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

## Security Audit

- Audited at: 2026-11-02T11:47:19.886\+00:00
- Summary: 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.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0