CD cargo-hosting
Put something on the internet from Cargo — hosted web apps (Vite by default, other static frameworks detected) and serverless edge workers that answer HTTP requests, plus the deployments that build and promote them, the env vars and secrets a worker reads, running a worker locally, and custom domains and search indexing for public sites. Triggers: "build me a dashboard for this", "host this app", "give me a URL to share", "deploy this", "I need a webhook endpoint", "make it live", "promote to production", "ship a UI for my team", "give my worker an API token", "set a secret on the worker", "Missing CARGO_API_TOKEN", "my app cannot call my worker", "run the worker locally", "put it on my own domain", "make the site indexable by Google". Skip when: the app or worker should be declared as committed workspace code — use cargo-project.
Put something on the internet from Cargo — hosted web apps (Vite by default, other static frameworks detected) and serverless edge workers that answer HTTP…
As a process D 46/100 · Unfinished process — References files that are not bundled: ../cargo-workspace-management/SKILL.md, ../cargo/references/prerequisites.md, ../cargo-billing/SKILL.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-usereferences/examples/workers.md:74Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl "https://api.getcargo.io/v1/hosting/env-vars?workerUuid=<worker-uuid>" -H "Authorization: Bearer $CARGO_API_TOKEN"
fixture
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5039 tokens (recommended < 5000); move details to references/ - 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 - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 46/100
- 0Tools and files. 4 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 71 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5039 tokens
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (20 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 842: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +5Description quotes 15 example trigger phrases
- +4Structure: 16 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (10 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.