SKILLEMALL.ai

BF soul-in-sapphire

Generic long-term memory (LTM) operations for OpenClaw using Notion (2025-09-03 data_sources). Use for durable memory writes/search, emotion-state ticks, journal writes, and model-controlled subagent spawn planning via local JSON presets.

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

Generic long-term memory (LTM) operations for OpenClaw using Notion (2025-09-03 datasources).

As a process F 44/100 · Will not run — References files that are not bundled: scripts/notionctl.mjs

ProcedureNotionPersonal productivitytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
F
44/100
Will not run
References files that are not bundled: scripts/notionctl.mjs
Tools and files w 18
0
Result and completion w 14
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: soul-in-sapphire (modbender/skill-library-mcp)

How to improve

  1. The text references files that are not there: add them or drop the references.
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/notionctl.mjs

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: scripts/notionctl.mjs
  • 0Tools and files. 1 referenced file(s) missing: scripts/notionctl.mjs
  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 2 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 84 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2327 tokens
  • 100Progress reporting. Reports progress

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)
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • -38 of 13 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 238: enough signal without eating the budget
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 84 items
  • +4Has examples (8 code blocks)

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