BC trifle-auth
Authenticate with the Trifle API using Sign-In with Ethereum (SIWE). Manages wallet-based authentication, JWT token storage, and session management for the Trifle ecosystem.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:25High-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-tokenpackage-lock.json:48High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…jgR+Mkmf+D189…ihQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:105High-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-tokenpackage-lock.json:199High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…eyz+fNF6…T8Q=="
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:388High-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: 5. 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")
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 606 tokens
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 173: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: suspicious
This skill appears to do Trifle wallet login as advertised, but it handles wallet private keys and long-lived session tokens with enough scoping and storage concerns that users should review it carefully before installing.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026