AC kickbacks
Kickbacks.ai — an executable guide to earning passive income from AI tool waiting time. Covers 6 use cases: ① Getting Started — ("How to install Kickbacks" "How to earn money with Claude Code" "How does Kickbacks work") ② Understanding the Economics — ("How much can I earn" "How are ads priced" "What is 50% revenue share") ③ Advertiser Tools — ("How to advertise on Kickbacks" "How to bid on the spinner" "How much does an ad cost") ④ Troubleshooting — ("Kickbacks not working" "Extension not showing" "Status bar says incompatible") ⑤ Analytics & Earnings — ("How to check my balance" "How do payouts work" "How many impressions did I get") ⑥ Privacy & Security — ("Is Kickbacks safe" "Does it read my code" "Is it reversible") Trigger when users say: "Kickbacks" "Get paid for waiting" "Claude Code ads" "spinner money" "earn while coding" "Kickbacks.ai" "Discombobulating" "codex ads" "paid spinner" or mention: kickbacks / spinner / Claude Code monetize / Codex passive income / IDE extension.
Kickbacks.ai — an executable guide to earning passive income from AI tool waiting time. Covers 6 use cases: ① Getting Started — ("How to install Kickbacks"…
As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
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: 8. 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 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 37 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1774 tokens
- 100Running it twice. Mutating operations check current state
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 999: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 27 example trigger phrases
- +4Structure: 10 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.