SKILLEMALL.ai

BD Vector Memory Skill

Vector memory for Aister — search by meaning, not by grep!

modbender/skill-library-mcp Agent Skills author: modbender MIT 6 files body ≈ 1 432 tokens Open the sourcegithub.com analyzed 2 d ago

Vector memory for Aister — search by meaning, not by grep!

As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationDockerPostgreSQLInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
99
Quality 40%
62
Run on models
none yet
Process rating
D
41/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Dangerous commands cmd-shell-rc INSTALL.md:282
    Writes to a shell startup file (quoted — discussed, not commanded)
    fi' >> ~/.bashrc
    quoted

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 41/100

  • 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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 40Consistency. Frontmatter name (Vector Memory Skill) differs from the folder (aister-vector-memory)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 85Steps. 31 steps, 1 vague phrases
  • 100Execution cost. Instruction body is 1432 tokens
  • low 13 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 58: 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: 20 headings
  • +3Step-by-step instructions: 31 items
  • +4Has examples (4 code blocks)

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