BF fiverr-gig-automation
Automates Fiverr gig lifecycle — creates gigs, sends buyer offers/proposals, manages inbox, and collects reviews. No Fiverr API needed — uses browser automation (Selenium). Fiverr has 4M+ buyers and you can start selling in minutes.
As a process F 41/100 · Will not run — References files that are not bundled: /?t=settings&s=advanced, scripts/fiverr_gig_manager.py, scripts/buyer_offer_finder.py
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: 2. 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: /?t=settings&s=advanced - warning
missing-refreference to a missing file: scripts/fiverr_gig_manager.py - warning
missing-refreference to a missing file: scripts/buyer_offer_finder.py - warning
missing-refreference to a missing file: scripts/inbox_manager.py
Process rating: all ten parameters 41/100
- 0Tools and files. 4 referenced file(s) missing: /?t=settings&s=advanced, scripts/fiverr_gig_manager.py, scripts/buyer_offer_finder.py
- 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. 5 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 524 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 232: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.