SKILLEMALL.ai

AB comms-md-reader

Read and adapt to someone's COMMS.md before contacting them. Use when: (1) drafting a message, email, or outreach to someone who has a COMMS.md, (2) scheduling or proposing a call with someone who has a COMMS.md, (3) the user asks you to check someone's communication preferences, (4) you need to calibrate tone, channel, or timing for a message to a specific person.

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

Read and adapt to someone's COMMS.md before contacting them. Use when: (1) drafting a message, email, or outreach to someone who has a COMMS.md, (2)…

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

ProcedureSales and CRMtype 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
66/100
Nearly there
Inputs and preconditions w 11
0
When it triggers w 12
50
Tools and files w 18
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: 2. 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 66/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 60Failures and branches. 2 branches
    • 100Steps. 29 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1359 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress

    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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 367: enough signal without eating the budget
    • +4Structure: 12 headings
    • +3Step-by-step instructions: 29 items
    • +3Output format is stated explicitly
    • +4Has examples (0 code blocks)

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