BC agent-wallet-nwc-bridge
Expose a local @moneydevkit/agent-wallet as a Nostr Wallet Connect (NIP-47) wallet-service (systemd user service).
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-password-literalindex.js:154Hard-coded password / key literal (may be an example)const clientSecret = fromHex(randHex(32));
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:18High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…YUc+XNJZ…HgY+fazadNFWFaMK/2vye…OQw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:45High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…5Ue/+tX+nmkg…wNx+ulArw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:116High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…lAt+43pW…7yQ+gG3v…XGj+TxO+SS5dsThQIA==",
detector -
low Secrets in code
secret-high-entropy-tokenREADME.md:3High-entropy token-like string (may be an id, hash or a credential)[](https://clawhub.ai/kristapsk/agent-wallet-nwc-bridge)
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "repo"
Process rating: all ten parameters 58/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 551 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 114: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 8 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: suspicious
This wallet bridge is transparent about its purpose, but it needs review because its spending controls are weak and a documented receive/send permission split is not enforced by the code.
LLM: suspicious (high) · 11 Aug 2026