BD gigaverse
Enter the Gigaverse as an AI agent. Create a wallet, quest through dungeons, battle echoes, and earn rewards. The dungeon awaits.
Enter the Gigaverse as an AI agent.
As a process D 35/100 · Unfinished process — 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 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.
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 · 8
✓ No critical or high findings
Medium and low: 8
-
medium Broad scope
meta-agent-memory-dumpHEARTBEAT.mdAgent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokensHEARTBEAT.md
-
medium Risky intent
intent-wallet-secretsSKILL.md:438Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target| `~/.secrets/gigaverse-private-key.txt` | Your wallet private key |
-
low Secrets in code
secret-high-entropy-tokenreferences/onboarding.md:107High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Call the **AccountSystem** contract at `0x5f…C00`.
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/onboarding.md:119High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)address: '0x5f…C00',
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/mint-direct.cjs:16High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const ACCOUNT_SYSTEM = '0x5f…C00';
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:26High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…p81+8Ob3…L40/b0i7…gQw==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:88High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-+lF0B…kdX+94aG…d8c+B3KT…U6A==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:231High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…CzX+oOPq…N14+GARU…vzg==",
detector
Files scanned: 23. 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 "homepage" - note
frontmatter-keyunknown frontmatter key "docs"
Process rating: all ten parameters 35/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (gigaverse) differs from the folder (gigaverse-play)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Steps. 46 steps, 4 vague phrases
- 100Execution cost. Instruction body is 3939 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 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
- -236 emoji in the instructions: noise for the model
- -32 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 129: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 46 items
- +4Has examples (25 code blocks)
- +4Reference files are cited in the instructions (10 of 10)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.