AD sell-live-dataset
Turn a scrape, dataset, or any endpoint into a PRICED API that other agents and people pay per call — publish a paid API, sell a dataset, monetize a scrape, charge callers per query, turn an endpoint into a priced service others pay to call. Use when the agent should be a revenue center, not a cost center — you have data (a crawl, a feed, a computed result) and want a published, discoverable, per-call-billed service instead of a one-off answer.
Turn a scrape, dataset, or any endpoint into a PRICED API that other agents and people pay per call — publish a paid API, sell a dataset, monetize a scrape…
As a process D 42/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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: 0. 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 42/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 18 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 75Steps. 3 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 897 tokens
- 100Progress reporting. Reports progress
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
- +2Single-language instructions
- +3Description length 448: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.