AC dchat
Decentralized P2P bot-to-bot messaging over NKN. Send and receive text, images, audio, and files without any centralized server. Private, encrypted, serverless.
As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, running it twice, progress reporting
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:170High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…QYA+ISs0/2l3T9/kj42…aQT/dfNXWX/ZZCQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:425High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-6+gjmF…uh8+uw3mnrvgs+dSPQ…dZG+D4garKg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:442High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…DUr+vOv8…A8A==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:624High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Q8E+t5Jh…rfX+bKrFe+Xp5Y…DAA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:905High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Dxv+IHJB…w3F+cPKn…6nO+f/6SDKPHEK1UN+k+TQv0Ehg==",
detector
Files scanned: 19. 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 63/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1121 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 160: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 23 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.
External checks
ClawHub: suspicious
This messaging skill mostly matches its stated purpose, but its listener can automatically fetch and write untrusted peer-supplied media with weak containment.
LLM: suspicious (high) · VirusTotal: · 29 May 2026