AB karpak-life-register
Automate Karpak Life registration and SBT minting on the Karpak Living Map. Activate when user asks to register/mint an SBT.
Automate Karpak Life registration and SBT minting on the Karpak Living Map.
As a process B 71/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting
ProcedureData and analyticsAI and agentstype and topics are labelled automatically from the skill text
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenregister-and-mint.mjs:37High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)sbtContract: '0x75…241',
detector -
low Secrets in code
secret-high-entropy-tokenregister-and-mint.mjs:45High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)sbtContract: '0x98…1C5',
detector
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 124 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
Process rating: all ten parameters 71/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 60Consistency. The Hermes dialect needs category and tags
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 8 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 1791 tokens
- low 12 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
- +1No license
- +2Single-language instructions
- +3Description length 124: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.
External checks
ClawHub: suspicious
The skill’s wallet registration and minting flow is coherent, but its unauthenticated local browser bridge creates a real tampering risk during wallet signing and transaction approval.
LLM: suspicious (high) · VirusTotal: · 9 Jul 2026