ext-preflight

Validate browser extension build artifacts and platform requirements for store submission.

Updated May 12, 2026
One-click install
npx skills add https://github.com/YeomanYe/skills --skill ext-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ext-preflight
Source: https://github.com/YeomanYe/skills/tree/main/ext-preflight
Command: npx skills add https://github.com/YeomanYe/skills --skill ext-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before publishing browser extensions, this Skill runs a comprehensive preflight check to ensure all platform requirements are met and outputs a clear pass/fail report with actionable remediation notes.

Core Features & Use Cases

  • Validates per-platform build artifacts (Chrome Web Store, Firefox AMO, Microsoft Edge) for expected files like manifest.json and packaged artifacts (.xpi for Firefox, .zip/.crx for others).
  • Verifies essential assets (icon, screenshots) meet platform requirements, and checks for missing resources.
  • Checks platform-specific preconditions (Firefox 2FA, Edge plan registration, Chrome developer account and privacy policy) and provides guided remediation steps.
  • Generates a structured report highlighting blocking items that must be fixed before submission and warnings that are non-blocking.

Quick Start

Run the ext-preflight preflight to generate a complete report and pause the release process until all blocking items are resolved.

Frequently Asked Questions about ext-preflight

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run preflight checks before publishing a browser extension?

To run preflight checks before publishing a browser extension, use this Skill to validate build artifacts, manifest files, and platform-specific requirements. It outputs a structured pass or fail report with actionable remediation steps to fix blocking items.

What are the submission requirements for Chrome Web Store and Firefox AMO extensions?

Chrome Web Store and Firefox AMO extensions require valid manifest.json files, specific packaged artifacts like .zip or .xpi, and verified assets. Chrome requires a developer account and privacy policy, while Firefox AMO requires 2FA for submission.

Can I validate Microsoft Edge extension build artifacts before submission?

Yes, you can validate Microsoft Edge extension build artifacts before submission. The Skill checks packaged artifacts, verifies essential assets like icons and screenshots, and confirms Edge-specific preconditions such as plan registration to ensure readiness.

Why does my browser extension fail store submission requirements?

Your browser extension fails store submission requirements due to missing resources, invalid manifest configurations, or unmet platform-specific preconditions. The preflight validation identifies these blocking items and provides guided remediation steps to resolve them.

Does preflight validation check for missing icons and screenshots in extension packages?

Yes, preflight validation checks for missing icons and screenshots in extension packages. It verifies that essential assets meet platform-specific requirements across Chrome Web Store, Firefox AMO, and Microsoft Edge, returning warnings for non-blocking issues.

ext-preflight: what does it do for extension publishing workflows?

The ext-preflight Skill performs comprehensive preflight validation across Chrome Web Store, Firefox AMO, and Microsoft Edge. It pauses the release process, enforcing blocking criteria through manifest checks and asset verification until all issues are resolved.