Content
86%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A strong, deployment-focused skill body: fully executable CLI commands with a decision guide and a cleanly split two-file bundle for configuration and emulation details. The main improvement opportunities are removing the redundant Description section that duplicates the frontmatter and adding an explicit post-deploy verification checkpoint.
Suggestions
Remove or shrink the '## Description' section, which repeats the frontmatter description nearly verbatim, and fold the Blaze billing note into the deploy workflow where the prerequisite actually matters.
Add a post-deploy verification step to the deploy-from-source workflow, e.g. `npx -y firebase-tools@latest apphosting:backends:get my-app-id` or fetching the backend URL to confirm the rollout succeeded before reporting completion.
Include a minimal `apphosting.yaml` example inline (run config, env vars, one `secret:` reference) so users can complete step 2 without necessarily opening the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean — concrete commands, no explanation of concepts Claude already knows — but the "## Description" section ("This skill enables the agent to deploy and manage modern, full-stack web applications...") restates the frontmatter description almost verbatim, and the Hosting vs App Hosting bullets add mild redundancy. Fits the 4 anchor (efficient with minor trimmable instances) better than 3, since padding is limited to the redundant opening section, and better than 5, which requires every token to earn its place. | 4 / 5 |
Actionability | Commands are copy-paste ready and complete: a full `firebase.json` apphosting block, `apphosting:backends:create --backend my-app-id --primary-region us-central1 --root-dir /`, the piped `secrets:set`/`secrets:grantaccess` pair, `deploy`, and the CI/CD `rollouts:create` variant. Matches the 5 anchor (executable, covers common cases); it does not fall to 4 since no minor gaps in the core flows are evident. | 5 / 5 |
Workflow Clarity | The deploy-from-source flow is a clearly sequenced numbered list with a conditional checkpoint ("Create the backend if it does not exist (`apphosting:backends:list`...)" with a quota fallback) and explicit do/don't guidance for CI/CD vs local deploys. It sits at 4 rather than 5 because there is no post-deploy verification step (e.g., checking rollout/backend status or the resulting URL), and it stays above 3 since the destructive/batch cap doesn't apply and one checkpoint is present. | 4 / 5 |
Progressive Disclosure | The body is a well-organized overview (~95 lines) that clearly signals two one-level-deep references — "see [Configuration](references/configuration.md)" and "See [Emulation](references/emulation.md)" — both of which exist as real files with no nested references of their own. Matches the 5 anchor (clear overview, well-signaled one-level-deep references, easy navigation) rather than 4, which expects organization gaps that are not present. | 5 / 5 |
Total | 18 / 20 Passed |