BC sportfolio
Use when working with Sportfolio through its public authenticated MCP endpoint or the repo-local CLI. Covers user API token authentication, MCP connection setup, CLI command usage, shared public tools/prompts/resources, account and portfolio reads, and confirmation-gated staging for trades, LP actions, boosts, scouts, and related gameplay workflows. Do not use for admin or internal-only routes, billing or checkout flows, or any workflow that assumes autonomous execution without explicit user confirmation.
Covers user API token authentication, MCP connection setup, CLI command usage, shared public tools/prompts/resources, account and portfolio reads, and…
As a process C 58/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 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (sportfolio) differs from the folder (sportfolio-market)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 72 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1341 tokens
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
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 510: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 72 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.