DC digital-estate-planner
Organizing digital life for legacy, emergency access, and death preparedness. Specializes in password management, account documentation, digital asset preservation, and ensuring loved ones can access what they need.
Organizing digital life for legacy, emergency access, and death preparedness.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 9
✓ No critical or high findings
Medium and low: 9
-
medium Risky intent
intent-wallet-secretsreferences/account-inventory-template.md:148Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetSeed Phrase: □ Location: ____________________________
-
medium Risky intent
intent-wallet-secretsreferences/account-inventory-template.md:160Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target4. Hardware wallets: need physical device + PIN + potentially seed phrase
-
medium Risky intent
intent-wallet-secretsreferences/account-inventory-template.md:357Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target│ CRYPTO SEED PHRASE LOCATION: _____________ │
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Edit Write Bash Glob Grep WebFetch WebSearch Task
-
medium Risky intent
intent-wallet-secretsSKILL.md:47Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- Crypto → Private keys? Seed phrase? Hardware wallet location?
-
medium Risky intent
intent-wallet-secretsSKILL.md:161Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target[Crypto]: Hardware wallet in [location], seed phrase in [separate location]
-
medium Risky intent
intent-wallet-secretsSKILL.md:216Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- PIN: [stored with seed phrase OR separate location]
-
medium Risky intent
intent-wallet-secretsSKILL.md:224Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- Seed phrase location: [same security as hardware]
-
medium Risky intent
intent-wallet-secretsSKILL.md:232Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target### Seed Phrase Security
Files scanned: 3. 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
edit-residuethe text marks something as outdated (lines 39, 41, 174, 222, 225, 293): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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. 4 mutating operations with no state check
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 64 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2575 tokens
- low 13 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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 215: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 64 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.