SKILLEMALL.ai

AF cargo-context

Read and write the workspace GTM knowledge base — the git-backed repository of markdown describing ICPs, personas, plays, proof points, objections, competitors, and signals — plus its runtime sandbox and typed knowledge graph. Triggers: "document our ICP", "write up this persona", "what is our positioning", "add a battlecard", "capture this objection", "what do we know about <segment>", "update our context", "what is in the context repo", "who do we sell to". Skip when: discovering who actually buys from you by analyzing won/lost data — that is cargo-gtm (this skill writes the conclusion down, it does not derive it); storing structured records rather than prose — use cargo-storage; attaching documents to an agent for RAG — use cargo-content.

ClawHub Agent Skills author: Cargo v1.3.0 MIT-0 10 files body ≈ 4 053 tokens Open the sourceclawhub.ai analyzed 25 h ago

Read and write the workspace GTM knowledge base — the git-backed repository of markdown describing ICPs, personas, plays, proof points, objections…

As a process F 48/100 · Will not run — References files that are not bundled: ../cargo-workspace-management/SKILL.md, ../cargo-ai/SKILL.md, ../cargo/references/prerequisites.md

GeneratorSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
F
48/100
Will not run
References files that are not bundled: ../cargo-workspace-management/SKILL.md, ../cargo-ai/SKILL.md, ../cargo/references/prerequisites.md
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
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: 10. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../cargo-workspace-management/SKILL.md
  • warning missing-ref reference to a missing file: ../cargo-ai/SKILL.md
  • warning missing-ref reference to a missing file: ../cargo/references/prerequisites.md
  • warning missing-ref reference to a missing file: ../cargo-content/SKILL.md
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 48/100

Will not run. References files that are not bundled: ../cargo-workspace-management/SKILL.md, ../cargo-ai/SKILL.md, ../cargo/references/prerequisites.md
  • 0Tools and files. 4 referenced file(s) missing: ../cargo-workspace-management/SKILL.md, ../cargo-ai/SKILL.md, ../cargo/references/prerequisites.md
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4053 tokens
  • 85Steps. 25 steps, 2 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • low The response is described with custom markup (4 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 9 example trigger phrases
  • +3Description length 751: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 25 items
  • +4Has examples (13 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)

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

External checks

ClawHub: suspicious
The skill is mostly transparent about managing a Cargo context repository, but it combines immediate repository writes with an unpinned CLI install and a broad shell-execution command that users should review carefully.
LLM: suspicious (high) · 3 Sept 2026