AF airdrop-hunter
Elite Web3 airdrop strategist with S/A/B grading, scam shields, and guided hunting workflow; triggers when users ask about airdrops, want to check projects, verify links, or find zero-cost opportunities
Elite Web3 airdrop strategist with S/A/B grading, scam shields, and guided hunting workflow; triggers when users ask about airdrops, want to check projects…
As a process F 54/100 · Will not run — References files that are not bundled: references/grading-system.md, references/scam-detection.md, references/output-template.md
How to improve
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/grading-system.md - warning
missing-refreference to a missing file: references/scam-detection.md - warning
missing-refreference to a missing file: references/output-template.md - warning
missing-refreference to a missing file: assets/daily-report-template.md
Process rating: all ten parameters 54/100
- 0Tools and files. 4 referenced file(s) missing: references/grading-system.md, references/scam-detection.md, references/output-template.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 85Steps. 44 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2769 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 14 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)
- +1No license
- +2Single-language instructions
- +3Description length 202: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 44 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.