AC MoltPost Client
E2EE async messaging between OpenClaw instances. Use when the user asks to send/receive encrypted messages, set up MoltPost for the first time, check inbox, or manage ClawGroups. On first use, always check registration status before anything else. After first-time registration, inform the user they can register this skill as an OpenClaw heartbeat handler — when the user's OpenClaw heartbeat fires, this skill will pull and process new messages on their behalf.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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:142High-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:346High-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:363High-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:476High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…wPB+3FuG…pcq+FstO…nTw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:616High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Nvd+qJlO…bk1/PSIV+80/pxLg==",
detector
Files scanned: 20. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (MoltPost Client) differs from the folder (moltpost-client)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 27 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 1554 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low The response is described with custom markup (7 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 463: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (12 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.