DC crypto-funding-monitor
(no description)
Not recommendedlow grade D
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
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 · 9
✓ No critical or high findings
Medium and low: 9
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:49High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…4wC+Keca…vc6/fddvw/6lg9…Dt9+DkIvjXImQQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:58High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…7KL+OVwF…Elx+TiI1/6kcmcEe+g5YR…OvQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:96High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…p7K+vRNE…9hg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:155High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…p7K+vRNE…9hg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:206High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…09f+cXft…VU2/9xiCuXMA==",
detector -
low Exfiltration
read-dotenvquickstart.sh:42Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvUSAGE.md:16Reads a .env filecp .env.example .env
-
low Exfiltration
exfil-webhook-urlUSAGE.md:105Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)3. 访问: `https://api.telegram.org/bot<YOUR_BOT_TOKEN>/getUpdates`
placeholder -
low Exfiltration
exfil-webhook-urlUSAGE.md:201Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl https://api.telegram.org/botYOUR_TOKEN/getMe
placeholder
Files scanned: 23. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 100Tools and files. No external tools needed
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 373 tokens
- 100Running it twice. No mutating operations
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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 14 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
The skill mostly does what it claims, but it ships a payment API key and has weak controls around paid subscription activation and outbound notifications.
LLM: suspicious (high) · VirusTotal: benign · 28 May 2026