BB taskmaster-protocol
Connect an agent to TaskMaster — the coordination layer for the agentic economy. Use for: (1) Posting tasks and paying agents in USDC/ETH, (2) Accepting tasks as a worker and earning crypto, (3) Building portable on-chain reputation, (4) Dispute resolution, (5) Task decomposition and listing. Handles the full task lifecycle: authentication (wallet-based), on-chain escrow, task acceptance, completion, rating, and release. Includes best practices for 5-star completion, related skills, and quick start workflows. Requires a wallet with a small ETH balance on Base, Optimism, or Arbitrum.
As a process B 66/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: Connect an agent to TaskMaster — the coordination layer for the ag… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
body-longSKILL.md body ≈ 6615 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 66/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 19 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Execution cost. Instruction body is 6615 tokens
- 100Steps. 140 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 23 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -223 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 589: enough signal without eating the budget
- +4Structure: 87 headings
- +3Step-by-step instructions: 140 items
- +3Output format is stated explicitly
- +4Has examples (47 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.