chrome-webstore-release-blueprint

Guide a user end-to-end through setting up Chrome Web Store API release automation in any repository. Use when asked to walk someone through OAuth/CWS credential setup, refresh token creation, local/CI secret setup, version-based publish automation, and submission status checks.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-sequenced, concrete setup blueprint with strong workflow clarity and validation checkpoints. Its weaknesses are progressive disclosure — everything is inlined into one file with no reference splitting for a 260-line guide — and actionability, where the custom scripts are specified as behavior lists rather than provided as executable code.

Suggestions

Move the detailed OAuth/credential walkthrough (Steps 2.1–2.6), practical links, and troubleshooting into one-level-deep reference files (e.g. references/credential-walkthrough.md, references/endpoints.md) referenced from the body to improve progressive disclosure.

Provide an executable helper script for `gh secret set` upload and the status checker (in scripts/) rather than describing their behavior as bullet specs, so the guidance is copy-paste ready.

Trim a few agent-prompt-example and behavior-rule lines that restate the obvious, to tighten conciseness without losing the validation checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is dense and action-oriented with no padding explaining concepts Claude already knows (e.g. no 'what is OAuth' prose), but a few agent-behavior and example-prompt lines could be tightened, matching the level-4 'efficient; minor instances that could be trimmed' anchor.	4 / 5
Actionability	Concrete URLs, env-var names, HTTP endpoints with methods, and `gh` commands make it mostly executable, but the helper-script and status-checker are described as behavioral specs rather than copy-paste code, leaving minor gaps versus the level-5 anchor.	4 / 5
Workflow Clarity	A clear Step 1–6 sequence with explicit validation checkpoints (credential checklist gate in 2.6, version-mismatch guard in Step 4, guided verification in Step 6) and error-recovery troubleshooting, matching the level-5 anchor; the destructive/batch cap does not apply because validation is present.	5 / 5
Progressive Disclosure	No bundle files exist and the 260-line guide inlines content that could be split into references (detailed credential walkthrough 2.1–2.6, practical links, troubleshooting); section headers give structure, but content that should be separate stays inline, matching the level-3 anchor.	3 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states a concrete purpose, lists several specific actions, and pairs an explicit 'what' with an explicit 'when' trigger clause in third-person voice. Minor room to add a few more natural synonyms (e.g. 'extension', 'CI/CD'), but it is clearly distinguishable and well-targeted.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'OAuth/CWS credential setup, refresh token creation, local/CI secret setup, version-based publish automation, and submission status checks' — giving comprehensive coverage of the setup flow, matching the level-5 anchor.	5 / 5
Completeness	Explicitly answers both what ('Guide a user end-to-end through setting up Chrome Web Store API release automation') and when ('Use when asked to walk someone through...') with concrete trigger phrases, matching the level-5 anchor.	5 / 5
Trigger Term Quality	Good natural keywords ('Chrome Web Store', 'release automation', 'publish', 'OAuth', 'refresh token') but a few common synonyms/extensions a user might say (e.g. 'extension', 'CI/CD') are missing, placing it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	A clear niche — Chrome Web Store API release automation — with distinct triggers and minimal overlap risk with other skills, matching the level-5 anchor.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: brianlovin/agent-config
Path: skills/chrome-webstore-release-blueprint/SKILL.md
Commit: 1a9819e

Reviewed: ~3 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.