AC crypto-supply-dilution-tracker
Analyzes crypto token supply dilution risk by comparing circulating supply against max/total supply using the free CoinGecko API (no key required). Use this for crypto trading, whale watching, tokenomics due diligence, DeFi research, and passive income / portfolio risk screening when you need to know how much future token supply could still enter circulation and dilute holders. Computes a dilution score and risk label (FULLY DILUTED, LOW, MODERATE, HIGH DILUTION RISK) per coin, supports scanning the top N coins by market cap or specific coin IDs, and outputs a readable table or JSON. Complements token unlock calendars and vesting schedule tools by giving a fast, no-signup supply-side sell-pressure proxy for crypto, defi, and whale-tracking workflows.
Analyzes crypto token supply dilution risk by comparing circulating supply against max/total supply using the free CoinGecko API (no key required).
As a process C 59/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 59/100
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 494 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)
- +1No license
- +2Single-language instructions
- +3Description length 760: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 6 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.