CB nostrkey
Cryptographic identity SDK for AI agents — generate Nostr keypairs, sign events, encrypt messages, BIP-39 seed phrases, portable backup tokens. 69 tests, zero C dependencies.
As a process B 67/100 · Nearly there — weak spots: result and completion, when it triggers, running it twice
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.
Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
-
medium Risky intent
intent-wallet-secretsSKILL.md:60Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target> Are we starting fresh, or do you have a 12-word seed phrase from a previous identity?"
-
medium Risky intent
intent-wallet-secretsSKILL.md:62Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target### Step 2a -- New identity (if they say new/fresh/no seed phrase)
-
medium Risky intent
intent-wallet-secretsSKILL.md:86Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target> **My seed phrase (write this down NOW):**
-
medium Risky intent
intent-wallet-secretsSKILL.md:89Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target> This seed phrase is the ONLY way to recover my identity if something goes wrong. Not the passphrase -- the seed phrase. Write it down on paper, or save it in a password manager, or put it in a safe.
-
medium Risky intent
intent-wallet-secretsSKILL.md:91Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target> If we lose this seed phrase, this identity is gone forever. No recovery, no reset, no support ticket. The math does not care.
Files scanned: 6. 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 "env"
Process rating: all ten parameters 67/100
- 0Result and completion. Does not say what the result is
- 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
- 70Failures and branches. 6 branches
- 100Tools and files. No external tools needed
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2823 tokens
- 100Progress reporting. Reports progress
- 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 174: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.