AF cargo-segmentation
Define and use segments — named, saved filters over a Cargo model that become the audience for a batch run, a play trigger, or an export. Triggers: "build a segment of", "filter my contacts where", "who matches this criteria", "save this as a list", "how many companies match", "the Closed-Won segment", "everyone who has not been emailed", "target only accounts that", "what is in this segment", "narrow this down to". Filter JSON uses `conjonction` (not `conjunction`) — misspelling it fails silently. Skip when: running something over the segment — use cargo-orchestration; exporting its rows — use cargo-analytics; ad-hoc SQL over the model — use cargo-storage.
Define and use segments — named, saved filters over a Cargo model that become the audience for a batch run, a play trigger, or an export.
As a process F 40/100 · Will not run — References files that are not bundled: ../cargo-orchestration/references/filter-syntax.md, ../cargo/references/prerequisites.md, ../cargo-analytics/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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../cargo-orchestration/references/filter-syntax.md - warning
missing-refreference to a missing file: ../cargo/references/prerequisites.md - warning
missing-refreference to a missing file: ../cargo-analytics/SKILL.md - warning
missing-refreference to a missing file: ../cargo-orchestration/SKILL.md - warning
missing-refreference to a missing file: ../cargo-orchestration/references/examples/plays.md - warning
missing-refreference to a missing file: ../cargo-observability/SKILL.md - warning
missing-refreference to a missing file: ../cargo-gtm/SKILL.md - warning
missing-refreference to a missing file: ../cargo-cdk/SKILL.md - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 40/100
- 0Tools and files. 8 referenced file(s) missing: ../cargo-orchestration/references/filter-syntax.md, ../cargo/references/prerequisites.md, ../cargo-analytics/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2688 tokens
- low 11 top-level sections: this looks like several domains in one skill
- 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 10 example trigger phrases
- +3Description length 665: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.