SKILLEMALL.ai
GitHub ↗ RU Sign in

AD foam-notes

Work with Foam note repositories. Create, edit, link, and tag notes. Get intelligent wikilink and tag suggestions. Skill supports backlinks discovery, daily notes, templates, graph visualization, note deletion, and renaming. Full Foam documentation included for easy querying.

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

Work with Foam note repositories.

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

IntegrationVS CodeGitHubObsidianDockerWriting and documentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 48/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
    • 30Running it twice. 22 mutating operations with no state check
    • 85Steps. 93 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3549 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)
    • +3Output format is not stated: the model decides each time
    • -5TODO / placeholder text left in the skill
    • -31 of 12 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 276: enough signal without eating the budget
    • +4Structure: 36 headings
    • +3Step-by-step instructions: 93 items
    • +4Has examples (20 code blocks)
    • +4Reference files are cited in the instructions (7 of 7)

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