SKILLEMALL.ai

AB claimable-postgres

Provision instant temporary Postgres databases via Claimable Postgres by Neon (pg.new) with no login, signup, or credit card. Supports REST API, CLI, and SDK. Use when users ask for a quick Postgres environment, a throwaway DATABASE_URL for prototyping/tests, or "just give me a DB now". Triggers include: "quick postgres", "temporary postgres", "no signup database", "no credit card database", "instant DATABASE_URL", "npx get-db", "pg.new", "pg.new API", "claimable postgres API".

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

Provision instant temporary Postgres databases via Claimable Postgres by Neon (pg.new) with no login, signup, or credit card. Supports REST API, CLI, and SDK.…

As a process B 70/100 · Nearly there — weak spots: inputs and preconditions

ProcedurePostgreSQLAI and agentsDesigntype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
B
70/100
Nearly there
Inputs and preconditions w 11
0
Tools and files w 18
60
Result and completion w 14
60
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: 1. 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 70/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 60Tools and files. Uses tools (web, node) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 85Steps. 33 steps, 1 vague phrases
    • 100Failures and branches. 3 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2397 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 11 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

    • +4Description does not say when NOT to use the skill (false activations)
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 10 example trigger phrases
    • +3Description length 482: enough signal without eating the budget
    • +4Structure: 21 headings
    • +3Step-by-step instructions: 33 items
    • +3Output format is stated explicitly
    • +4Has examples (9 code blocks)

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