SKILLEMALL.ai

AF cargo-cdk

Manage a whole Cargo workspace as code — declare connectors, models, plays, tools, agents, MCP servers, segments, context, folders, files, workers, and apps in TypeScript, then reconcile them with `cargo-ai cdk` (init → types → plan → deploy), the way you would run Pulumi or the AWS CDK. Triggers: "as code", "in git", "version-controlled", "reproducible", "Terraform for Cargo", "set up a whole workspace", "staging and production", "deploy from CI", "review this in a PR", "cargo.state.json", "scaffold from a template", "is there a cookbook for this", "start from a cookbook". Skills with a CDK example (TAM building, account scoring, contact sourcing, routing, AI SDR, rep cockpit) live in gtm-skills; menu in references/cookbooks.md. Skip when: it is a one-off operation, a read, or an ad-hoc query — use the matching capability skill.

ClawHub Agent Skills author: Cargo v1.2.4 MIT-0 16 files body ≈ 4 154 tokens Open the sourceclawhub.ai analyzed 2 d ago

Manage a whole Cargo workspace as code — declare connectors, models, plays, tools, agents, MCP servers, segments, context, folders, files, workers, and apps…

As a process F 54/100 · Will not run — References files that are not bundled: ../cargo/references/prerequisites.md, ../cargo/SKILL.md, ../cargo-orchestration/references/node-diagram.md

ProcedureTerraformAWSSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
F
54/100
Will not run
References files that are not bundled: ../cargo/references/prerequisites.md, ../cargo/SKILL.md, ../cargo-orchestration/references/node-diagram.md
Tools and files w 18
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 16. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../cargo/references/prerequisites.md
  • warning missing-ref reference to a missing file: ../cargo/SKILL.md
  • warning missing-ref reference to a missing file: ../cargo-orchestration/references/node-diagram.md
  • warning missing-ref reference to a missing file: ../cargo-gtm/references/cost-discipline.md
  • warning missing-ref reference to a missing file: ../cargo-observability/SKILL.md
  • warning missing-ref reference to a missing file: ../cargo-mailbox-management/SKILL.md
  • warning missing-ref reference to a missing file: ../cargo-workspace-management/SKILL.md
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 54/100

Will not run. References files that are not bundled: ../cargo/references/prerequisites.md, ../cargo/SKILL.md, ../cargo-orchestration/references/node-diagram.md
  • 0Tools and files. 7 referenced file(s) missing: ../cargo/references/prerequisites.md, ../cargo/SKILL.md, ../cargo-orchestration/references/node-diagram.md
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 58 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4154 tokens
  • 100Steps. 25 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • low The response is described with custom markup (7 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 841: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 13 example trigger phrases
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 25 items
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.

External checks

ClawHub: suspicious
This appears to be a legitimate Cargo infrastructure-as-code skill, but it should be reviewed because it uses mutable npm/npx installs in workflows that can deploy or delete workspace resources.
LLM: suspicious (high) · 10 Sept 2026