AF cargo-storage
Work with the data inside a Cargo workspace — models (Companies, Contacts, Deals…), datasets, columns, relationships, records, and SQL over workspace storage. Triggers: "what models do I have", "show me the schema", "add a column for", "how many contacts do I have", "SELECT … FROM", "query my companies table", "join contacts to companies", "what is the DDL", "set up a webhook-fed model", "where does this field live", "import this into a model", "unify these models", "merge duplicate accounts", "link contacts to companies", "set up a relationship between". Skip when: querying run or batch telemetry rather than business data — use cargo-orchestration; naming a reusable filtered audience — use cargo-segmentation.
Work with the data inside a Cargo workspace — models (Companies, Contacts, Deals…), datasets, columns, relationships, records, and SQL over workspace storage.
As a process F 32/100 · Will not run — References files that are not bundled: ../cargo/references/prerequisites.md, ../cargo/references/interaction.md, ../cargo-diagnostics/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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
net-credential-usereferences/examples/ingest-webhook.md:91Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -X POST "$BASE/v1/models/$MODEL_UUID/records/ingest?token=$TOKEN" \
fixture -
low Exfiltration
net-credential-usereferences/examples/ingest-webhook.md:96Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -X POST "$BASE/v1/models/$MODEL_UUID/records/ingest?token=$TOKEN" \
fixture
Files scanned: 10. 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/references/interaction.md - warning
missing-refreference to a missing file: ../cargo-diagnostics/SKILL.md - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 32/100
- 0Tools and files. 3 referenced file(s) missing: ../cargo/references/prerequisites.md, ../cargo/references/interaction.md, ../cargo-diagnostics/SKILL.md
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3323 tokens
- 100Progress reporting. Reports progress
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (12 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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 15 example trigger phrases
- +3Description length 719: enough signal without eating the budget
- +4Structure: 14 headings
- +4Has examples (17 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.