BC create-token
Guide for creating a token on Nad.fun. Covers the full 4-step flow - uploading an image, uploading metadata, mining a salt for a vanity address, and deploying the token on-chain via the BondingCurveRouter contract.
As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:31High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)BondingCurveRouter = "0x6F…A22"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:32High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Lens = "0x7e…7ea"
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected flow-seq-start at node end at line 4, column 23: argument-hint: [name] [symbol] ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (create-token) differs from the folder (nadfun-token-creation)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 19 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1716 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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 214: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.
External checks
ClawHub: suspicious
This skill matches its token-creation purpose, but it asks users to rely on an unpinned wallet skill and can submit irreversible value-spending blockchain transactions without a required final confirmation step.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026