BD clawdio
Secure P2P communication for AI agents via Telegram. Simple onboarding: create "Clawdio Hub" group, add bot, share keys. Noise XX handshake, XChaCha20-Poly1305 encryption, connection consent, human verification.
As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
AnalyzerTelegramInfrastructureAI and agentsSecuritytype and topics are labelled automatically from the skill text
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-password-literalsrc/crypto.ts:8Hard-coded password / key literal (may be an example)export interface KeyPair { publicKey: Uint8Array; secretKey: Uint8Array; } -
low Secrets in code
secret-high-entropy-tokensrc/crypto.ts:58High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const protocolName = sodium.from_string('Nois…E2b');quoted
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: Secure P2P communication for AI agents via Telegram. Simple onboar… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 44/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. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (clawdio) differs from the folder (clawdiocomms)
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 32 steps
- 100Execution cost. Instruction body is 1184 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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
- +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
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 211: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: suspicious
This skill mostly matches its secure agent messaging purpose, but it includes under-disclosed key storage and a startup script that can run unreviewed background code from a hard-coded local path.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026