BF gcp-project-bootstrap
Create and bootstrap Google Cloud projects for new workloads. Use when the user wants to create a new Google Cloud project, choose a project ID and naming convention, decide billing and region setup, enable required Google APIs, prepare service accounts, or initialize a project for Cloud Run, Vertex AI, BigQuery, Cloud Storage, or Firebase. Also use when auditing whether a planned GCP project setup is complete before deployment.
As a process F 55/100 · Will not run — References files that are not bundled: references/project-creation-checklist.md, references/billing-and-apis.md, references/common-gcloud-commands.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/project-creation-checklist.md - warning
missing-refreference to a missing file: references/billing-and-apis.md - warning
missing-refreference to a missing file: references/common-gcloud-commands.md
Process rating: all ten parameters 55/100
- 0Tools and files. 3 referenced file(s) missing: references/project-creation-checklist.md, references/billing-and-apis.md, references/common-gcloud-commands.md
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (gcp-project-bootstrap) differs from the folder (awen)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 4 branches
- 85Steps. 46 steps, 1 vague phrases
- 100Execution cost. Instruction body is 619 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 432: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 46 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.