AB maverick-exa
Exa MCP workflow for web and people research plus hosted MCP server setup using a fixed tool set (`web_search_exa`, `web_search_advanced_exa`, `people_search_exa`). Use for requests to run Exa web discovery, constrained/advanced Exa queries, person/profile lookup, troubleshoot Exa MCP tool or rate-limit issues, or produce concise source-linked research summaries from Exa results.
As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, progress reporting
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-secret-in-urlreferences/exa-mcp-setup.md:16Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)`https://mcp.exa.ai/mcp?exaApiKey=…&tools=…
placeholder -
low Exfiltration
exfil-secret-in-urlreferences/exa-mcp-setup.md:27Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)"url": "https://mcp.exa.ai/mcp?exaApiKey=…&tools=…"
placeholder
Files scanned: 4. 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 68/100
- 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
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 390 tokens
- 100Running it twice. No mutating operations
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 382: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 14 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.