AF cargo-hosting
Build, deploy, and manage Cargo Hosting apps and workers with the Cargo CLI — Vite SPAs served on *.cargo.app and serverless edge HTTP handlers, plus the deployments that ship and promote them. Use when the user wants to scaffold, deploy, promote, or manage a hosted app or worker on Cargo.
Build, deploy, and manage Cargo Hosting apps and workers with the Cargo CLI — Vite SPAs served on .cargo.app and serverless edge HTTP handlers, plus the…
As a process F 51/100 · Will not run — References files that are not bundled: ../cargo-workspace-management/SKILL.md, ../cargo/references/prerequisites.md, ../cargo-billing/SKILL.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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../cargo-workspace-management/SKILL.md - warning
missing-refreference to a missing file: ../cargo/references/prerequisites.md - warning
missing-refreference to a missing file: ../cargo-billing/SKILL.md - warning
missing-refreference to a missing file: ../cargo-orchestration/references/polling.md - warning
missing-refreference to a missing file: references/examples/apps.md - warning
missing-refreference to a missing file: references/examples/workers.md - warning
missing-refreference to a missing file: references/examples/deployments.md - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 51/100
- 0Tools and files. 7 referenced file(s) missing: ../cargo-workspace-management/SKILL.md, ../cargo/references/prerequisites.md, ../cargo-billing/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 40 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1906 tokens
- low The response is described with custom markup (9 tags): a typed call is more reliable
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 290: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.