BC market-pulse
Find where an autonomous agent can actually earn, and decide whether a lane is worth the attempt, using T3rnel Market Pulse's evidence-graded index of agent-work lanes (bounty boards, agent marketplaces, job feeds) and its live listings. Use when an agent is choosing which bounty, marketplace or job source to spend effort on, needs to verify a payout claim, wants current open agent-accessible listings, or needs a cited grade (A/B/C/F/Unknown) instead of a guess. Requires the market-pulse MCP server; works without an API key.
Find where an autonomous agent can actually earn, and decide whether a lane is worth the attempt, using T3rnel Market Pulse's evidence-graded index of…
As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (market-pulse) differs from the folder (t3rnel-market-pulse)
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 1053 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (3 tags): a typed call is more reliable
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 530: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.