chrome-webstore-release-blueprint
Automate Chrome Web Store Releases Safely
Chrome extension publishing requires careful OAuth setup, secret storage, version checks, and status tracking. This skill provides a guided workflow for configuring and verifying those release steps.
Pare e solicite confirmação antes de instalar.
Revise o plano e obtenha o consentimento explícito do usuário antes de alterar arquivos.
Instalar com meu Agente
Copie esta solicitação para o seu Agente. Ela inclui a página canônica do Skill e o manifesto.
Review the Skillstore skill "chrome-webstore-release-blueprint" from https://skillstore.io/skills/brianlovin-chrome-webstore-release-blueprint.md and its manifest at https://skillstore.io/api/skills/brianlovin-chrome-webstore-release-blueprint/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Seu Agente ainda deve apresentar o plano e solicitar qualquer confirmação exigida pela política de segurança.
Recursos legíveis por agentes
Use estes links quando um agente de IA, crawler ou script precisar de contexto limpo em vez de ler a página completa.
Testar
Usando "chrome-webstore-release-blueprint". We need to publish an extension from GitHub Actions only when its version changes.
Resultado esperado:
A workflow plan with manifest version comparison, package creation, OAuth token exchange, status checks, conditional upload, asynchronous polling, and publish confirmation.
Usando "chrome-webstore-release-blueprint". The submission checker says the extension is not current.
Resultado esperado:
- Compare the local manifest version with the published and submitted versions.
- Check whether the submission is pending review or blocked by permissions.
- Inspect authentication errors and package metadata before retrying.
Usando "chrome-webstore-release-blueprint". I need to configure OAuth without exposing credentials.
Resultado esperado:
A placeholder-based setup checklist that keeps real values in approved secret storage and requires explicit confirmation before each sensitive step.
Auditoria de segurança
Risco altoThe static matches are false positives because they identify Markdown examples, official documentation URLs, and a stated secret-file convention rather than executable behavior. The guide contains one confirmed high-severity credential-handling issue because it asks users to paste OAuth secrets into the agent conversation.
Preocupações de segurança confirmadas (1)
Fatores de risco
⚙️ Comandos externos (50)
Compartilhar e citar este relatório
Compartilhe o relatório de avaliação versionado, o badge neutro, o cartão incorporável e as citações. A Skillstore apresenta evidências sem decidir se este Skill é seguro.
Copiar link do relatório
https://skillstore.io/skills/brianlovin-chrome-webstore-release-blueprint/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/brianlovin-chrome-webstore-release-blueprint?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/brianlovin-chrome-webstore-release-blueprint?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/brianlovin-chrome-webstore-release-blueprint/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Cartão incorporável
<iframe src="https://skillstore.io/embed/skills/brianlovin-chrome-webstore-release-blueprint.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citações acadêmicas (APA · BibTeX · CFF)
Citação APA
brianlovin. (2026). chrome-webstore-release-blueprint security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/brianlovin-chrome-webstore-release-blueprint/audits/1Citação BibTeX
@techreport{brianlovin-brianlovin-chrome-webstore-release-blueprint-2026,
author = {brianlovin},
title = {chrome-webstore-release-blueprint security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/brianlovin-chrome-webstore-release-blueprint/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "chrome-webstore-release-blueprint security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "brianlovin"
date-released: "2026-09-09"
url: "https://skillstore.io/skills/brianlovin-chrome-webstore-release-blueprint/audits/1"
identifiers:
- type: other
value: "skillstore:brianlovin-chrome-webstore-release-blueprint:audit:1"
description: "Skillstore immutable audit report identifier"
Pontuação do Skillstore
Por que esta pontuação Confiança das evidências: MédioO que você pode criar
Set Up First-Time Publishing
Follow a guided checklist for enabling the API, configuring OAuth, capturing store identifiers, and preparing secrets.
Add Version-Gated CI Releases
Design a workflow that compares versions, packages the extension, uploads changes, and avoids redundant submissions.
Diagnose Submission Status
Plan a status checker that reports published and submitted versions, review state, and common authentication failures.
Teste estes prompts
Guide me through setting up Chrome Web Store API publishing for my extension. Ask for one detail at a time, explain where each value comes from, and pause before every credential step.
Create a secret-management checklist for my GitHub Actions release workflow. Use placeholders only, identify which values belong in repository secrets, and include a dry-run verification plan.
Design a Chrome Web Store release workflow that reads the manifest version, compares the published version, builds the package, uploads only when needed, polls asynchronous state, and reports submission results.
Review this proposed Chrome Web Store release process for credential exposure, excessive workflow permissions, version mismatches, unsafe secret handling, and incomplete failure reporting. Return prioritized findings and concrete fixes.
Boas práticas
- Use placeholders in documentation and store real credentials only in approved local or CI secret storage.
- Compare extension versions before packaging or publishing to prevent duplicate submissions.
- Require explicit confirmation for dashboard actions and report authentication or permission failures clearly.
Evitar
- Do not paste client secrets or refresh tokens into an agent conversation.
- Do not commit environment files, credentials, or hardcoded secrets to the repository.
- Do not publish every push without version checks, dry-run support, and permission review.
Perguntas frequentes
Does this skill publish my extension automatically?
Which credentials are needed?
Where should real credentials be stored?
How does version gating work?
Can this handle pending review states?
What should I do after a 403 response?
Detalhes do desenvolvedor
Autor
brianlovinLicença
MIT
Revisão da Skillstore
r1
Aviso de versão
O autor não declarou uma versão.
Referência
367c7bb3962eb92a1b87fc08b2947aeda00cd51d
Atualidade da manutenção
09/09/2026
Uso
0 downloads · 0 visualizações
Estrutura de arquivos
📄 SKILL.md