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.
安裝前請停止並請求確認。
請審查安裝計畫，並在變更檔案前取得使用者明確同意。
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
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.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「chrome-webstore-release-blueprint」。 We need to publish an extension from GitHub Actions only when its version changes.
預期結果:
A workflow plan with manifest version comparison, package creation, OAuth token exchange, status checks, conditional upload, asynchronous polling, and publish confirmation.
正在使用「chrome-webstore-release-blueprint」。 The submission checker says the extension is not current.
預期結果:
- 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.
正在使用「chrome-webstore-release-blueprint」。 I need to configure OAuth without exposing credentials.
預期結果:
A placeholder-based setup checklist that keeps real values in approved secret storage and requires explicit confirmation before each sensitive step.
安全審計
高風險The 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.
已確認的安全問題 (1)
風險因素
⚙️ 外部命令 (50)
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/brianlovin-chrome-webstore-release-blueprint/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/brianlovin-chrome-webstore-release-blueprint?utm_source=security_passport_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>嵌入卡片
<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>學術引用 (APA · BibTeX · CFF)
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/1BibTeX 引用
@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"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
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.
試試這些提示
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.
最佳實務
- 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.
避免
- 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.
常見問題
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?
開發者詳細資訊
作者
brianlovin授權
MIT
Skillstore 修訂
r1
版本提示
作者未聲明版本。
引用
367c7bb3962eb92a1b87fc08b2947aeda00cd51d
維護新鮮度
2026/9/9
使用量
0 次下載 · 0 次瀏覽
檔案結構
📄 SKILL.md