firefox-extension-dev
/firefox-extension-dev
Służy jako baza wiedzy dla agenta do dodatków Firefoksa: manifest.json, API browser.*, wysyłka do AMO i web-ext CLI.
- Autor
- acaprino ↗
- Repozytorium
- alfio-claude-plugins ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 7
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Służy jako baza wiedzy dla agenta do dodatków Firefoksa: manifest.json, API browser.*, wysyłka do AMO i web-ext CLI.
Oryginalny opis (EN)
Reference knowledge base behind the firefox-extension-dev-agent agent. TRIGGER WHEN: any Firefox WebExtension or add-on work touching manifest.json, browser.* APIs, AMO submission or the web-ext CLI.
Jak działa
- Reference Files
Podgląd SKILL.md
--- name: firefox-extension-dev description: > Reference knowledge base behind the firefox-extension-dev-agent agent. TRIGGER WHEN: any Firefox WebExtension or add-on work touching manifest.json, browser.* APIs, AMO submission or the web-ext CLI. --- <daodan_host_binding host="claude"> This binding governs execution of this package and its loaded references. It takes precedence over executable examples written for another host. Use only registered tools and their actual input schema; an example never creates a tool, argument, permission, model alias or nested worker capability. Preserve the generated worker allowlist, dependency closure, scope and delivery contracts. Claude binding: repository tools are Read/Glob/Grep and Write/Edit; shell execution uses Bash and network fetch uses WebFetch. Pass the executable string in Bash's command field, and use its registered timeout/background schema. Worker dispatch uses the available native Agent mechanism and its registered agent-selection and prompt fields. Do not turn a prose role label into an invented role argument. Inherit the session model unless the declared workflow and active schema permit an override. Load installed skills by qualified ID; named roles use their owning plugin's agent identity, while workflow entries use /<plugin>:<workflow>. Required foreign providers use Claude's marketplace/install commands: claude plugin marketplace add <source>, then claude plugin install <provider>@<marketplace>. A provider that is installed but disabled is enabled with claude plugin enable <provider>@<marketplace>; check `claude plugin list --json` before the first phase, and stop with that command when any plugin of this package's dependency closure, direct or transitive, is off. A declared package MCP server is configured through the generated MCP manifest; still check its tools are actually available in the active session. The executing agent and its coordinator own continuation, recovery, verification and delivery. Skills supply knowledge and method instructions; they are not executors or a runtime persistence mechanism. Resolve each component by kind and exact installed identity. A role is dispatched as a worker, a skill loads instructions, and a workflow starts its declared method. Kernel owner-qualified skill references are logical provider identities: resolve them to the actual host registry name and verified installed provider path. Do not invent a registry string by adding an owner's prefix when the host does not use it. Do not load an agent identity as a skill or execute a workflow name as a shell command. Declared required foreign providers remain mandatory. If a required provider or capability (including required MCP access or isolation) is unavailable, stop its dependent phase and report the missing capability. Optional external providers follow the method's declared selection and absence behavior; their absence alone does not block the base workflow. Report any explicitly requested but unavailable provider contribution as unfulfilled and continue independent work. Do not install a different host's plugin or substitute unrelated skills to claim coverage. Shell execution alone does not establish interactive stdin. Before a capture or checkpoint, use an available session-control mechanism. When stdin is unavailable, keep user-driven capture in a supported background process with bounded output and an explicit stop signal controlled by the coordinator after the user's completion message. Close owned browser/process resources on completion or cancellation. Continue working within the current authorization while the requested result is achievable. After a tool error, inspect its cause, correct the relevant input or implementation, retry when justified and verify the outcome; never repeat a failing action blindly. Do not close the turn with a promise or a partial result when an authorized next step can still produce or verify the requested result. Stop only for a documented real impediment, a missing required capability, an unresolved human decision or the caller's stop request. At that boundary, report completed results, remaining work and the concrete prerequisite for continuation; continue any independent work that the blocker does not prevent. A tool's successful exit, a worker stop or an idle session is not the deliverable. Return final text naming observed findings, artifact paths, executed checks and blockers. An empty worker result is missing delivery: inspect or resume that worker when permitted, or record failure. Verify required artifacts and candidate gates before marking the requested outcome complete. This is an execution binding, not a rewrite of source examples. Preserve programming language fences, domain code and host APIs that are the subject of marketplace-ops or agent-sdk-builder. A host-as-subject API is not a tool provided to this session. Compiled binding and static checks do not prove an installed host executed a run. </daodan_host_binding> # Firefox Extension Development References This skill provides reference files for the `firefox-extension-dev-agent` agent. The agent handles all active development work (scaffolding, coding, debugging, publishing). These reference files serve as its knowledge base. ## Reference Files - `references/browser-api-reference.md` - Complete list of all 51 browser.* APIs with methods, events, and permissions - `references/manifest-schema.md` - Full manifest.json key reference with MV2/MV3 examples - `references/amo-publishing.md` - AMO publishing checklist, review policies, CSP, security best practices, i18n - `references/mdn-api-urls.md` - Direct MDN URL index for all browser.* APIs, manifest keys, and Extension Workshop resources - `references/best-practices.md` - Best practices, pitfalls, and anti-patterns: JS patterns, Workers, sessions, startup, security, performance, cross-browser
Pliki w paczce (7)
- SKILL.md 6 KB
- SKILL.toml 1 KB
- references/amo-publishing.md 10 KB
- references/best-practices.md 33 KB
- references/browser-api-reference.md 10 KB
- references/manifest-schema.md 10 KB
- references/mdn-api-urls.md 14 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki 68aa7ee02633 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90agent-browser-extension-developer
Działa jako subagent specjalista od rozszerzeń Chrome, Firefox i międzyprzeglądarkowych: Manifest V3, service workers, content scripts, WebExtension API i migracja z MV2. - 100browser-extension-patterns
Buduje rozszerzenia przeglądarek z Manifest V3 dla Chrome, Firefox i zgodności międzyprzeglądarkowej: skrypty treści, workery w tle, interfejs popup, API pamięci i komunikacja rozszerzeń. - 100browser-extension-builder
Buduje rozszerzenia przeglądarek dla Chrome, Firefox i międzyprzeglądarkowe: architektura rozszerzenia, Manifest V3, skrypty treści, interfejsy popup, strategie monetyzacji i publikacja w Chrome Web Store. - 90browser-extension-developer
Wspiera tworzenie rozszerzeń Chrome, Edge i Firefox: cykl życia service workera w Manifest V3, wybór interfejsu, wstrzykiwanie skryptów, model uprawnień i długotrwałe zadania. - 100upgrade-browser
Podnosi wersje przeglądarek Chrome lub Firefox w testach Flutter Web Engine i Framework. - 100firefox-cli
Steruje Firefoksem użytkownika z terminala: nawigacja, karty i okna, zrzuty ekranu, odczyt DOM, oczekiwanie i interakcje na stronie w zalogowanej sesji.