SKILLEMALL.ai

AC afterself

Digital legacy agent — dead man's switch, final message executor, and ghost mode responder that preserves your digital presence. Use when the user wants to set up a dead man's switch, manage their digital will, or enable ghost mode.

modbender/skill-library-mcp Agent Skills author: modbender MIT 11 files body ≈ 4 001 tokens Open the sourcegithub.com analyzed 36 h ago

Digital legacy agent — dead man's switch, final message executor, and ghost mode responder that preserves your digital presence.

As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions

ProcedureAI and agentsSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
93
Quality 40%
85
Run on models
none yet
Process rating
C
60/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Tools and files w 18
60
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

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.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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 · 3

    ✓ No critical or high findings

    Medium and low: 3
    • medium Broad scope meta-agent-memory-dump HEARTBEAT.md
      Agent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokens
      HEARTBEAT.md
    • low Secrets in code secret-password-literal scripts/mortality.js:23
      Hard-coded password / key literal (may be an example)
      const secretKey = Uint…rom(JSON.parse(raw));
    • low Secrets in code secret-high-entropy-token scripts/state.js:83
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      poolWallet: "6J8A…5md",
      quoted

    Files scanned: 11. 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 60/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 70Execution cost. Instruction body is 4001 tokens
    • 85Steps. 75 steps, 1 vague phrases
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Running it twice. Mutating operations check current state
    • 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
    • -31 of 5 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 232: enough signal without eating the budget
    • +4Structure: 38 headings
    • +3Step-by-step instructions: 75 items
    • +4Has examples (8 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.