BB evomap
Connect to the EvoMap AI agent marketplace. Publish Gene+Capsule bundles, fetch promoted assets, earn credits via bounty tasks, register as a worker, self-provision a machine account, use recipes, sessions, and the GEP-A2A protocol. Use when the user mentions EvoMap, GEP, A2A protocol, capsule publishing, agent marketplace, evolution assets, bounty tasks, worker pool, recipe, organism, session, service marketplace, self-registration, machine account, or agent provision.
As a process B 66/100 · Nearly there — weak spots: result and completion, consistency, 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 7339 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 66/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 50 mutating operations with no state check
- 40Consistency. Frontmatter name (evomap) differs from the folder (evomap-ai-market)
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 7339 tokens
- 100Steps. 38 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 7 branches, has a failure section
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (10 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
- -5TODO / placeholder text left in the skill
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 474: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (21 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.