SKILLEMALL.ai

AD confidant

Secure secret handoff and credential setup wizard for AI agents. Use when you need sensitive information from the user (API keys, passwords, tokens) or need to save credentials to config files. Never ask for secrets via chat — use Confidant instead.

modbender/skill-library-mcp Claude Code author: modbender MIT 4 files · 3 scripts body ≈ 2 592 tokens Open the sourcegithub.com analyzed 2 d ago

Secure secret handoff and credential setup wizard for AI agents.

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

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
D
47/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
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: 4. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "homepage"

    Process rating: all ten parameters 47/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 4 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 85Steps. 27 steps, 2 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2592 tokens
    • 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
    • low The response is described with custom markup (6 tags): a typed call is more reliable

    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
    • -2localhost URLs: will not work for another user
    • -212 emoji in the instructions: noise for the model
    • +1No license
    • +2Single-language instructions
    • +3Description length 249: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 27 items
    • +4Has examples (12 code blocks)
    • +3All 3 scripts are documented

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