AB trading212-api
This skill should be used when the user asks to "connect to Trading 212", "authenticate Trading 212 API", "place a trade", "buy stock", "sell shares", "place market order",, "place pending order", "place limit order", "cancel order", "check my balance", "view account summary", "get positions", "view portfolio", "check P&L", "find ticker symbol", "search instruments", "check trading hours", "view dividends", "get order history", "export transactions", "generate CSV report", or needs guidance on Trading 212 API authentication, order placement, position monitoring, account information, instrument lookup, or historical data retrieval.
This skill should be used when the user asks to "connect to Trading 212", "authenticate Trading 212 API", "place a trade", "buy stock", "sell shares", "place…
As a process B 70/100 · Nearly there — weak spots: inputs and preconditions, execution cost
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:89High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **API Key (ID)** (e.g., `3583…yPF`)
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:90High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **API Secret** (e.g., `7MOz…tlo`)
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:112High-entropy token-like string (may be an id, hash or a credential)export T212…DER="Basic $(echo -n "3583…tlo" | base64)"
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 10892 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 70/100
- 30Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 10892 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 85Steps. 31 steps, 2 vague phrases
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +5Description quotes 21 example trigger phrases
- +3Description length 638: enough signal without eating the budget
- +4Structure: 65 headings
- +3Step-by-step instructions: 31 items
- +3Output format is stated explicitly
- +4Has examples (46 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.