ib-trades-history

Fetch trade executions from Interactive Brokers filtered by account, date range, or symbol. Supports live API (~7 days history) and FlexReport (full history). Use when user asks about their trades, executions, or transaction history. Requires TWS or IB Gateway running locally.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An actionable, well-structured skill body with executable commands, a clear source-selection matrix, and a reconciliation checkpoint. It could tighten explanatory prose and formalize the connection-fallback loop into explicit validation steps.

Suggestions

Tighten the Spread Grouping and Output prose: move the iron-condor max_risk caveat and reconciled-P&L explanation into a short note rather than full paragraphs, keeping commands and field lists primary.

Render the port-fallback sequence as an explicit validate->retry->verify checklist (e.g. '1. Try configured port; 2. If it fails, retry the other port; 3. Verify connection; 4. Persist the working account type to memory') rather than a narrative description.

If the script grows further, split detailed output-field semantics into a references/OUTPUT.md file referenced from SKILL.md so the overview stays lean.

Dimension	Reasoning	Score
Conciseness	Largely lean and well-organized with executable commands, but the Spread Grouping and Output sections include some explanatory prose about reconciled P&L and iron-condor caveats that could be trimmed without losing actionability.	4 / 5
Actionability	Copy-paste ready, executable commands covering the common cases (recent trades, symbol filter, FlexReport, file source, date range, spread grouping) plus a complete argument list and documented env-var fallback.	5 / 5
Workflow Clarity	Clear source-selection workflow with a validation checkpoint (spread_grouping.reconciled asserts P&L equality and the doc tells Claude to check it before trusting), but the connection fallback sequence is described narratively rather than as an explicit validate->retry->verify loop.	4 / 5
Progressive Disclosure	Body is a clear overview pointing to one real bundle file (scripts/trades.py) and dependency trading-skills; sections are well-organized and the script reference path is real, though all detail lives in the single script rather than split across reference files.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that concretely states capabilities, data sources, and explicit trigger conditions with a relevant prerequisite. Only minor gap is the absence of a few synonyms a user might naturally say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (fetch trade executions, filter by account/date range/symbol) and two distinct data sources (live API and FlexReport) with comprehensive coverage of capability.	5 / 5
Completeness	Explicitly answers what ('Fetch trade executions... filtered by account, date range, or symbol') and when ('Use when user asks about their trades, executions, or transaction history') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases like 'their trades, executions, or transaction history' but lacks file-extension or synonym-level coverage (e.g. 'fills', 'trade log'); good but a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche (IB trade-execution history) with distinct triggers tied to a specific broker and prerequisite (TWS/IB Gateway); minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: staskh/trading_skills
Path: .claude/skills/ib-trades-history/SKILL.md
Commit: 9a1bf57

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.