SKILLEMALL.ai

BF logseq

Provide commands for interacting with a local Logseq instance through its Plugin API. Use for creating pages, inserting blocks, querying the graph database, managing tasks, retrieving content, or automating workflows in Logseq. Only works with a locally running instance with the API enabled; default port or set path expected for [$API accessible skill].

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

Provide commands for interacting with a local Logseq instance through its Plugin API.

As a process F 38/100 · Will not run — References files that are not bundled: ...args, references/api-types.md

ProcedureGitHubSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
F
38/100
Will not run
References files that are not bundled: ...args, references/api-types.md
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

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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ...args
  • warning missing-ref reference to a missing file: references/api-types.md

Process rating: all ten parameters 38/100

Will not run. References files that are not bundled: ...args, references/api-types.md
  • 0Tools and files. 2 referenced file(s) missing: ...args, references/api-types.md
  • 0Result and completion. Does not say what the result is
  • 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
  • 30Running it twice. 6 mutating operations with no state check
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 38 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1862 tokens

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
  • -42 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 355: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 38 items
  • +4Has examples (8 code blocks)

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