ib-create-consolidated-report

Consolidate IBRK trade CSV files from a directory into a summary report. Groups trades by symbol, underlying, date, strike, buy/sell, and open/close. Outputs both markdown and CSV.

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/ib-create-consolidated-report/SKILL.md

Quality

Content

68%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.

The body is concise, actionable, and well-structured with a real backing script, but as a batch operation it lacks any validation or verification step, which caps workflow clarity.

Suggestions

Add a verification step, e.g. confirm CSV files match expected IBRK columns before consolidating and check that the generated markdown/CSV are non-empty and internally consistent afterward.

Show an example invocation using --port to illustrate the unrealized P&L fetching path.

Replace tautological field glosses ('Strike - Strike price') with either meaningful detail or a simple comma-separated field list to tighten the consolidation-logic section.

Dimension	Reasoning	Score
Conciseness	The body is efficient and well-sectioned with no padding of concepts Claude already knows, though a few field glosses are tautological (e.g. 'Strike - Strike price', 'Put/Call - Option type'), placing it just below the lean 'every token earns its place' anchor.	4 / 5
Actionability	It provides the full executable command signature and two copy-paste example invocations, but the --port flag (used to fetch unrealized P&L) is documented yet not shown in any example, leaving a minor gap.	4 / 5
Workflow Clarity	The skill is a single batch operation (processing an entire directory of CSV files) with an unambiguous command, but it includes no input validation or output verification checkpoint, so per the batch-operation cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Content is organized into clear sections (Instructions, Arguments, Consolidation Logic, Output, Example Usage, Timezone) with the implementation kept one level deep in scripts/consolidate.py referenced via the command, though there is no explicit navigational pointer to the script.	4 / 5
	Total	15 / 20 Passed

Description

62%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.

The description is specific and clearly occupies a distinct niche, but it omits any explicit 'when to use' trigger guidance, which caps completeness and leaves trigger-term coverage at a mid-level score.

Suggestions

Add a 'Use when...' clause with natural trigger phrases, e.g. 'Use when consolidating IBKR trade CSVs into a summary report or when the user asks to aggregate trade activity by symbol, strike, and open/close.'

Include common user-facing synonyms such as 'IBKR', 'Interactive Brokers', 'trade log', and 'P&L summary' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (IBRK trade CSV files) and several concrete actions — consolidating into a summary report, grouping by six fields, and outputting both markdown and CSV — with only minor coverage gaps, fitting the 'lists several specific actions' anchor better than the vague lower anchors.	4 / 5
Completeness	The 'what' is clearly stated (consolidate, group, output formats) but there is no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Relevant domain keywords like 'IBRK trade CSV', 'summary report', 'symbol', and 'strike' are present, but it lacks common natural variations or synonyms a user might say, so it sits at 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The IBKR-specific trade CSV consolidation niche with detailed grouping fields gives it distinct triggers and minimal conflict risk with other skills, matching the 'clear niche' anchor.	5 / 5
	Total	15 / 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-create-consolidated-report/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.