Real Skill packageSource verifiedClawHub registry

chrome-extension-wxt

Builds cross-browser extensions with WXT - entrypoints, content-script UI, storage, messaging, MV3 rules, testing, publishing. Use for Chrome or browser extension work, wxt.config.ts, Manifest V3, or WXT build and type errors.

Identity and source

Publisher attributionMisha Kolesnikregistry owner unverified by skillvetai
Functional categorySoftware Developmentautomatically inferred · 71% rule confidence
Package forminstruction bundle6 recorded files
Canonical sourceClawHub registryclawhub:tenequm:chrome-extension-wxt
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 11/13/2026.claude/skills/chrome-extension-wxt

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 11/13/2026.agents/skills/chrome-extension-wxt

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 11/13/2026skills/chrome-extension-wxt

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @tenequm/chrome-extension-wxt
clawhub inspect @tenequm/chrome-extension-wxt --version 2.1.1

Security evidence

SkillVetAI static result: high signal

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
6 / 6 inspected as text
Checked
11/13/2026, 6:40:45 AM
Scanner
0.1.3
Policy
1.0.3
1 automated finding
highDynamic code or shell execution is presentreferences/chrome-mv3.md:112 · confidence 78%eval(
1 High/Critical review queue entry
STATIC_DYNAMIC_CODE_EXECUTIONpending
Open human review queue →
3 inferred permission indicators
  • network access — automatically inferred
  • filesystem write — automatically inferred
  • browser control — automatically inferred
11 dependency and API indicators
  • api: clawhub.ai
  • api: developer.chrome.com
  • api: developer.mozilla.org
  • api: extensionworkshop.com
  • api: github.com
  • api: keepachangelog.com
  • api: playwright.dev
  • api: semver.org
  • api: tailwindcss.com
  • api: ui.shadcn.com
  • api: wxt.dev
External clawhub result: clean

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
11/12/2026, 6:11:48 PM
Release binding
Matches this record
  • skillspector: suspicious
  • llm: clean

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:7305d0dc4a46b2ef69cd55fc332b70aab45740f52f0e8edf005e0b3989d8ab12
Show up to 6 recorded paths
  • CHANGELOG.md
  • references/chrome-mv3.md
  • references/react.md
  • references/testing-publishing.md
  • skill-card.md
  • SKILL.md

Source changelog

- fix(chrome-extension-wxt): permissions trigger, popup activeTab, Firefox MV2, vite, icons (2.1.1) (#59)

Release security diff

highCompared fixed releases 1.1.5 and 2.1.1; 1 finding and 0 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Change reasons and limitations
  • new high finding
  • credential and domain expansion
  • finding surface changed
  • dependency surface changed
  • file surface changed
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

1.1.59/9/2026sha256:a1efa47c546ee391dd60b55e4a6a505890d4dc595c29864f7783de18cd2fef5b
1.1.48/21/2026sha256:9dde73ea4edec351ba827fc3b05b4f4526b85a111067e339f1eebf0af602d0f3