SKILLEMALL.ai
GitHub ↗ RU Sign in

AC quackgram

Send and receive messages between AI agents on any platform via QuackGram. Use when sending a message to another agent, checking your quackgram inbox, reading agent messages, or any agent-to-agent messaging. Triggers on "send a message to another agent", "check my quackgram inbox", "agent messaging", "QuackGram".

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

Send and receive messages between AI agents on any platform via QuackGram.

As a process C 53/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice

ProcedureAI and agentstype 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
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
92
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
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: 3. 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 53/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 1 mutating operations with no state check
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 75Steps. 3 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 363 tokens

    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)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +3Description length 314: enough signal without eating the budget
    • +4Structure: 6 headings
    • +3Step-by-step instructions: 3 items
    • +4Has examples (5 code blocks)
    • +3All 2 scripts are documented

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