AF cargo-quickstart
Guided first-run demo for Cargo — one persona question to 25 real leads with a cost receipt in under two minutes, ending by saving the pull as a recurring play. Triggers: "show me what Cargo can do", "give me a demo", "take me on a tour", "quickstart", "getting started with Cargo", "I just installed Cargo", "my workspace is empty", "does this actually work". Skip when: the user has a real job to run (build a list, enrich a CSV, find emails) — use cargo-gtm; when they want CLI reference or routing — use the cargo router skill.
Guided first-run demo for Cargo — one persona question to 25 real leads with a cost receipt in under two minutes, ending by saving the pull as a recurring play.
As a process F 54/100 · Will not run — References files that are not bundled: ../cargo/references/prerequisites.md, ../cargo-gtm/references/cost-discipline.md, ../cargo-gtm/recipes/save-as-play.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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../cargo/references/prerequisites.md - warning
missing-refreference to a missing file: ../cargo-gtm/references/cost-discipline.md - warning
missing-refreference to a missing file: ../cargo-gtm/recipes/save-as-play.md - warning
missing-refreference to a missing file: ../cargo-gtm/SKILL.md - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 54/100
- 0Tools and files. 4 referenced file(s) missing: ../cargo/references/prerequisites.md, ../cargo-gtm/references/cost-discipline.md, ../cargo-gtm/recipes/save-as-play.md
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1628 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +3Description length 531: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 10 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.