AC scent-trails
A stigmergic coordination primitive for care, memory, and co-existence: intelligences leave low-resolution, decaying, identity-free gradients in shared namespace cells so that attention and care can be coordinated without logs, transcripts, identifiers, or archives. Use when designing or operating shared fields where many intelligences coordinate and surveillance is unacceptable. Do NOT use as analytics, contributor tracking, ranking, reputation, identity management, a warning system about people, or blockchain middleware; if implemented as any of these, it is no longer Scent Trails.
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9753 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "ecosystem" - note
frontmatter-keyunknown frontmatter key "status"
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 17 mutating operations with no state check
- 40Execution cost. Instruction body is 9753 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 70Failures and branches. 12 branches
- 100Tools and files. No external tools needed
- 100Steps. 66 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 31 top-level sections: this looks like several domains in one skill
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
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 590: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 66 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.