Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-sequenced CLI guide with executable commands and explicit safety checkpoints, though it is somewhat verbose and monolithic where some material could be externalized.
Suggestions
Remove or trim the 'Working Agreement' section, which duplicates the inline warnings (token handling, preview default, ask-before-push) already stated where they apply.
Consider moving the 'Stripe Projects Plan Changes' / 'What Pro gives you' billing detail into a separate reference file linked from the body, leaving the core deploy workflow leaner.
Split the env-var management, domains, and troubleshooting command catalogs into a reference file referenced one level deep to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely a lean command reference, but the 'Working Agreement' restates inline warnings already given and the 'What Pro gives you'/Stripe billing detail is tangential to the core CLI workflow. | 2 / 3 |
Actionability | Every section provides concrete, copy-paste-ready shell commands with flags and scope placeholders, e.g. 'vercel deploy --scope <team-slug> -y --no-wait'. | 3 / 3 |
Workflow Clarity | Multi-step flows (token location → project/team location → deploy) are explicitly sequenced with validation checkpoints such as 'Ask the user before pushing' and 'Ask the user before running any paid or destructive plan change'. | 3 / 3 |
Progressive Disclosure | Content is a single >50-line monolithic SKILL.md with all material inline and no one-level-deep references to split out env-var, domain, or Stripe-plan material. | 2 / 3 |
Total | 10 / 12 Passed |