SKILLEMALL.ai

AB obsidian-bases

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 3 files body ≈ 814 tokens Open the sourcegithub.com analyzed 2 d ago

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of…

As a process B 73/100 · Nearly there — weak spots: result and completion, failures and branches, progress reporting

GeneratorObsidianWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
B
73/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
Result and completion w 14
40
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: obsidian-bases (sickn33/agentic-awesome-skills)

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"

    Process rating: all ten parameters 73/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 40Result and completion. Does not say what the result is
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 6 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 814 tokens
    • 100Running it twice. No mutating operations

    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
    • +1No license
    • +2Single-language instructions
    • +3Description length 256: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 6 items
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (1 of 2)

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