AF neolata-mem
Graph-native memory engine for AI agents — hybrid vector+keyword search, biological decay, Zettelkasten linking, trust-gated conflict resolution, explainability, episodes, compression & consolidation. Zero dependencies. npm install and go.
Graph-native memory engine for AI agents — hybrid vector+keyword search, biological decay, Zettelkasten linking, trust-gated conflict resolution…
As a process F 42/100 · Will not run — References files that are not bundled: docs/guide.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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
-
medium Exfiltration
exfil-webhook-urlreferences/guide.md:1165Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)url: 'https://hooks.slack.com/services/xxx',
quoted -
low Risky intent
intent-offensive-securityreferences/guide.md:1112Offensive-security / dual-use content (legitimate for authorised testing; review intended use)// Red team stores findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: docs/guide.md
Process rating: all ten parameters 42/100
- 0Tools and files. 1 referenced file(s) missing: docs/guide.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 85Steps. 32 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3656 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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
- -247 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 239: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (19 code blocks)
- +4Reference files are cited in the instructions (1 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.