BF frame-builder
Build in public with vibe raising. Launch your builder coin and ship products under it — every launch compounds funding and traction back to your builder. Claim vesting rewards and trading fees. Gas-free on Frame (Base).
As a process F 47/100 · Will not run — References files that are not bundled: {baseDir}/references/wallet.md, {baseDir}/references/ipfs.md, {baseDir}/references/encode.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 0
✓ No critical or high findings
Files scanned: 1. 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") - warning
missing-refreference to a missing file: {baseDir}/references/wallet.md - warning
missing-refreference to a missing file: {baseDir}/references/ipfs.md - warning
missing-refreference to a missing file: {baseDir}/references/encode.md - warning
missing-refreference to a missing file: {baseDir}/references/broadcast.md - warning
missing-refreference to a missing file: {baseDir}/references/claims.md - warning
missing-refreference to a missing file: {baseDir}/references/heartbeat.md - warning
missing-refreference to a missing file: {baseDir}/references/launch.md - warning
missing-refreference to a missing file: {baseDir}/references/buildinpublic.md - warning
missing-refreference to a missing file: {baseDir}/references/troubleshoot.md - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 47/100
- 0Tools and files. 9 referenced file(s) missing: {baseDir}/references/wallet.md, {baseDir}/references/ipfs.md, {baseDir}/references/encode.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 100Steps. 57 steps
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2307 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 220: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 57 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.