# Review a Chrome Website Decluttering Extension Guide

Planning a website decluttering extension requires clear feature requirements and development constraints. This public guide describes a no-build Manifest V3 approach, but does not include implementation files.

## Install

```bash
npx skillstore add nexaiguy/nex-clean-page-ext
```

## Metadata

- Status: approved
- Slug: nexaiguy-nex-clean-page-ext
- Version: 1.2
- Author version: 1.2
- Skillstore revision: r1
- Version status: invalid
- Tree hash: a78062be33bb6bf19dd5ab1e56318b21ecc9bb1cdf5aa42c05aabda5900d7cef
- Author: nexaiguy
- GitHub username: nexaiguy
- License: MIT
- Repository: https://github.com/nexaiguy/nex-ai-skills/tree/463aaff26593654193deb52f24d18e80ec21e323/skills/nex-clean-page-ext
- 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: network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/nexaiguy-nex-clean-page-ext
- Manifest: https://skillstore.pages.dev/api/skills/nexaiguy-nex-clean-page-ext/manifest

## Capabilities

- Describes a Manifest V3 extension approach using vanilla JavaScript, HTML, and CSS.
- Lists intended clutter categories, including popups, chat widgets, sticky headers, and social sidebars.
- Explains the intended use of chrome.storage for preferences and restoration states.
- Outlines manual extension reloading and the Chrome Load unpacked development workflow.
- Documents heuristic detection and the stated exclusion of iframe and Shadow DOM content.

## Use Cases

- Learn extension development concepts: Review the documented no-build approach, Manifest V3 terminology, and manual reload workflow before starting an extension project.
- Define decluttering requirements: Use the listed clutter categories, preference storage, and restoration goals to draft requirements for a separately implemented browser utility.
- Plan extension validation: Translate the guide's heuristic detection, restoration claims, and iframe exclusions into a test checklist for source obtained separately.

## Prompt Templates

### Summarize the guide

```
Summarize this skill's guide in plain language. Distinguish documented extension features from files actually included in this package.
```

### Explain the development workflow

```
Explain the no-build Manifest V3 workflow described in this guide. Identify the source files I must obtain before using Chrome's Load unpacked option.
```

### Draft implementation requirements

```
Turn the guide into requirements for a separately implemented extension. Cover clutter categories, reversible hiding, preferences, and unsupported DOM contexts.
```

### Create a verification plan

```
Create a validation plan for the described extension. Include dynamic pages, restoration, stored preferences, permission review, and iframe exclusions. Mark unverified claims.
```

## Limitations

- Only a Markdown guide is included; extension source, scripts, and templates are absent.
- Production readiness, Chrome Web Store acceptance, and complete reversibility are claims, not verified results.
- The described detection is heuristic and does not cover elements inside iframes or Shadow DOM.
- The described development workflow requires manual extension reloading after edits.

## Best Practices

- Confirm which implementation files are available before planning installation or publication.
- Review extension permissions and source before loading any separately obtained implementation.
- Test detection and restoration across representative sites before relying on the guide's compatibility claims.

## Anti Patterns

- Treating this documentation package as an installable extension.
- Reporting the guide's example output as files actually generated or included.
- Assuming heuristic hiding guarantees intact layouts or complete reversibility on every website.

## Security Audit

- Audited at: 2026-11-02T12:08:58.868\+00:00
- Summary: All four static findings are false positives: the flagged lines contain attribution or catalog links, not executable requests or reconnaissance commands. No evidence found of prompt injection, credential collection, or data exfiltration in the supplied guide. Extension source is absent, so its runtime behavior and security cannot be assessed.

## Stats

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