How do I install the Quasar Bex Development skill?

Run npx skillmds@latest add quasarframework/quasar-bex-development in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Quasar Bex Development safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Quasar Bex Development?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Quasar Bex Development free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Quasar Bex Development?

quasarframework (@quasarframework) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Quasar Bex Development by quasarframework

Name: Quasar Bex Development
Author: quasarframework

Quasar Bex Development

Build, configure, secure, debug, test, and package browser extensions with Quasar BEX mode. Use for extension manifests, Manifest V3, background service workers, content scripts, injected page scripts, popup and options pages, permissions, cross-context messaging, BEX bridge, Chrome or Firefox targets, store packaging, and `quasar dev` or `quasar build -m bex` workflows.

quasarframework 7b69114 2 files · 2.5 KB Updated Sep 17, 2026

File contents

Quasar Browser Extension Development

Use this skill with quasar-development for shared UI and application concerns.

Map extension contexts

Inspect quasar.config.* > bex, src-bex/manifest.json, background scripts, content scripts, injected scripts, popup/options pages, and bridge usage.
Read the current Quasar BEX documentation and target-browser extension documentation.
Add the mode with quasar mode add bex.
Identify each execution context and its available APIs before changing code.

Minimize privilege and trust

Request only required permissions, host permissions, and web-accessible resources.
Treat page DOM, page messages, storage, tabs, and external messages as untrusted input.
Validate message origin, shape, channel, and response before privileged actions.
Use the BEX bridge for supported cross-context communication; handle teardown and navigation cleanly.
Keep privileged APIs in the background context and expose narrow operations to content/UI contexts.
Respect Manifest V3 service-worker suspension: persist required state and do not rely on long-lived globals.
Avoid remote code and dynamic execution that violate browser store policies or CSP.
Account for API and manifest differences between Chrome-family browsers and Firefox.

Validate in target browsers

Run quasar dev -m bex -T chrome or the supported target and load the development extension.
Test installation, update, browser restart, tab navigation, service-worker restart, and permission denial/removal.
Test every content-script match pattern against intended and unintended pages.
Build with quasar build -m bex -T <target> and inspect the emitted manifest and package contents.
Run tests, typecheck, lint, formatting, and store-policy checks for each supported browser.

---name: quasar-bex-developmentdescription: Build, configure, secure, debug, test, and package browser extensions with Quasar BEX mode. Use for extension manifests, Manifest V3, background service workers, content scripts, injected page scripts, popup and options pages, permissions, cross-context messaging, BEX bridge, Chrome or Firefox targets, store packaging, and `quasar dev` or `quasar build -m bex` workflows.---# Quasar Browser Extension DevelopmentUse this skill with `quasar-development` for shared UI and application concerns.## Map extension contexts1. Inspect `quasar.config.* > bex`, `src-bex/manifest.json`, background scripts, content scripts, injected scripts, popup/options pages, and bridge usage.2. Read the current [Quasar BEX documentation](https://quasar.dev/quasar-cli-vite/developing-browser-extensions/introduction) and target-browser extension documentation.3. Add the mode with `quasar mode add bex`.4. Identify each execution context and its available APIs before changing code.## Minimize privilege and trust- Request only required permissions, host permissions, and web-accessible resources.- Treat page DOM, page messages, storage, tabs, and external messages as untrusted input.- Validate message origin, shape, channel, and response before privileged actions.- Use the BEX bridge for supported cross-context communication; handle teardown and navigation cleanly.- Keep privileged APIs in the background context and expose narrow operations to content/UI contexts.- Respect Manifest V3 service-worker suspension: persist required state and do not rely on long-lived globals.- Avoid remote code and dynamic execution that violate browser store policies or CSP.- Account for API and manifest differences between Chrome-family browsers and Firefox.## Validate in target browsers1. Run `quasar dev -m bex -T chrome` or the supported target and load the development extension.2. Test installation, update, browser restart, tab navigation, service-worker restart, and permission denial/removal.3. Test every content-script match pattern against intended and unintended pages.4. Build with `quasar build -m bex -T <target>` and inspect the emitted manifest and package contents.5. Run tests, typecheck, lint, formatting, and store-policy checks for each supported browser.

Frequently asked questions