AB fiverr-gig-optimizer
Coach Fiverr sellers (and Etsy/Creative Market gig-style platforms) on gig titles, descriptions, packaging, pricing, gig images/video, search ranking (Fiverr SEO), level progression, and reviewer-conversion. Diagnoses why a gig isn't getting impressions, why impressions aren't converting to orders, why repeat-buyer rate is low. Adapts advice for new sellers (level 0) vs Top Rated and Pro sellers. Use when asked to write or improve a Fiverr gig, raise impressions, raise conversion rate, structure pricing tiers, design gig images, write a gig video script, hit Level 1/2/Top Rated, or migrate clients off-platform. Triggers on "fiverr gig", "fiverr seo", "fiverr ranking", "gig impressions", "level up fiverr", "top rated", "fiverr pricing", "gig packaging", "creative market gig".
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, running it twice, 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: 2. 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 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 10 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 98 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2677 tokens
- low 13 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 9 example trigger phrases
- +3Description length 785: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 98 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.