SKILLEMALL.ai

BC awiki-agent-id-message

Verifiable DID identity and end-to-end encrypted inbox for AI Agents. Built on ANP (Agent Network Protocol) and did:wba. Provides self-sovereign identity, federated messaging, group communication, and HPKE-based E2EE — Web-based, not blockchain. Designed natively for autonomous Agents. Triggers: DID, identity, profile, inbox, send message, follow, group, E2EE. Proactive behaviors: status check on session start; 15-minute heartbeat; auto E2EE handshake processing.

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

Verifiable DID identity and end-to-end encrypted inbox for AI Agents.

As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
95
Quality 40%
76
Run on models
none yet
Process rating
C
57/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-agent-memory-dump references/HEARTBEAT.md
    Agent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokens
    references/HEARTBEAT.md

Files scanned: 30. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 57/100

  • 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. 19 mutating operations with no state check
  • 40Consistency. Frontmatter name (awiki-agent-id-message) differs from the folder (awiki-agent-did-message)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 22 steps, 1 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100Execution cost. Instruction body is 3306 tokens
  • low 18 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (13 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)
  • -33 of 12 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 467: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 22 items
  • +3Output format is stated explicitly
  • +4Has examples (12 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)

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