BD elite-longterm-memory-local
Local vector memory system with LanceDB + Pure JS embedding. No native modules or external APIs required.
Local vector memory system with LanceDB + Pure JS embedding.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:103High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…stJ+S5jm…auj+owDo…jmi/FnUp…mEg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:119High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…yVj+xz1d1RgWKs+rLSY…Esq+xfrd…rcg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:192High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…nOa+n+n5rE…eab/duDP…2Kw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:254High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…wQp+7C4n…9JQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:260High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Ezj+TLszyASooky+i742…H1Q==",
detector
Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "keywords"
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1274 tokens
- 100Running it twice. No mutating operations
- low 10 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 105: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +4Structure: 17 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.