# Explore a Chrome Extension Trust-Check Guide

Planning an AI text detection extension requires understanding its architecture and delivery requirements. This public guide outlines the intended design while disclosing missing source assets.

## Install

```bash
npx skillstore add nexaiguy/nex-trust-check
```

## Metadata

- Status: approved
- Slug: nexaiguy-nex-trust-check
- Version: 1.2
- Author version: 1.2
- Skillstore revision: r1
- Version status: invalid
- Tree hash: ddc4399ac79a3eb69891a7317e9fcaac5bc2917668f8389ecf3e64d72ede5180
- Author: nexaiguy
- GitHub username: nexaiguy
- License: MIT
- Repository: https://github.com/nexaiguy/nex-ai-skills/tree/463aaff26593654193deb52f24d18e80ec21e323/skills/nex-trust-check
- 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-trust-check
- Manifest: https://skillstore.pages.dev/api/skills/nexaiguy-nex-trust-check/manifest

## Capabilities

- Describes an intended Manifest V3 extension with a side panel and context menu integration.
- Lists relevant Chrome APIs, including activeTab, scripting, storage, and contextMenus.
- Outlines a no-build approach using vanilla JavaScript, HTML, and CSS.
- Explains the intended local heuristic analysis approach and its stated limitations.
- Describes manual unpacked installation after obtaining the separate extension source.

## Use Cases

- Assess a proposed extension: Review the documented architecture and missing deliverables before choosing a starting point for browser extension development.
- Evaluate review analysis requirements: Identify accuracy, privacy, and source availability questions before adopting a heuristic review analysis tool.
- Plan a source package evaluation: Use the guide to scope a technical evaluation without assuming that the extension source is included.

## Prompt Templates

### Summarize the guide

```
Summarize this guide and distinguish included documentation from extension assets that must be obtained separately.
```

### Explain the architecture

```
Explain the documented Manifest V3 components and Chrome APIs. Identify details that cannot be verified without source code.
```

### Prepare a validation checklist

```
Create a validation checklist for the separately obtained extension source, covering installation, permissions, local processing, selector maintenance, and detection accuracy.
```

### Assess an API integration proposal

```
Using only the guide, assess adding an external detection API. Separate documented claims from assumptions and identify consent, privacy, and credential requirements.
```

## Limitations

- Only the public guide is included; extension source, scripts, and templates are absent.
- No runnable detector or reproducible accuracy evaluation is provided.
- Local-only processing, production readiness, and browser compatibility claims cannot be verified from this guide.
- The described implementation excludes build-step frameworks and requires manual site selector updates.

## Best Practices

- Confirm that the separate source package contains the advertised components before planning deployment.
- Inspect actual extension permissions and network behavior before processing sensitive text.
- Validate heuristic scores against representative reviews and retain human review for consequential decisions.

## Anti Patterns

- Treating this documentation folder as a complete runnable extension.
- Presenting heuristic scores as definitive proof of AI authorship or review fraud.
- Assuming local-only processing or production readiness without examining the actual implementation.

## Security Audit

- Audited at: 2026-11-02T11:52:43.863\+00:00
- Summary: All six static findings are false positives involving Markdown formatting, informational links, or ordinary product descriptions. No evidence found of executable commands, reconnaissance, data exfiltration, or prompt injection in the supplied guide. Extension source is absent, so its advertised security and runtime behavior cannot be verified.

## Stats

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