ib-collar

Generate tactical collar strategy reports for protecting PMCC positions through earnings or high-risk events. Requires TWS or IB Gateway running locally.

Quality

62%

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-collar/SKILL.md

Quality

Content

71%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 actionable and well-sequenced with executable commands and a documented JSON contract, and the port-fallback logic adds a useful checkpoint. The main weaknesses are a missing referenced template file and inline content (report sections, key concepts) that could be split into separate reference files.

Suggestions

Create the referenced `templates/markdown-template.md` (or remove the dangling reference) so Step 2 has a real formatting source.

Move the 'Report Sections' and 'Key Concepts' detail into a separate reference file (e.g. `references/report-format.md`) and link to it from SKILL.md to improve progressive disclosure.

Add a brief validation/review checkpoint in Step 2 (e.g. confirm required JSON fields are present before generating the report) to strengthen the workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, JSON field listings, and section specs; the 'Key Concepts' block explains specialized PMCC/collar mechanics that Claude may not know, which is justified rather than padded.	4 / 5
Actionability	Provides an executable command (`uv run python scripts/collar.py SYMBOL [--port PORT] [--account ACCOUNT]`) with copy-paste examples and a documented JSON schema, but references a `templates/markdown-template.md` file that is not present in the bundle, leaving a minor gap.	4 / 5
Workflow Clarity	Steps 1-3 are clearly sequenced (gather data, format report, report results) and the port-fallback logic provides an explicit error-recovery checkpoint, though there is no validation step for the generated report content.	4 / 5
Progressive Disclosure	Content is well-sectioned but largely monolithic in SKILL.md (~107 lines with the JSON schema, report sections, and key concepts all inline), and it references a non-existent `templates/markdown-template.md` path; a real one-level-deep reference file would improve navigation.	3 / 5
	Total	15 / 20 Passed

Description

53%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 distinct, clearly stating what the skill does, but it omits an explicit 'Use when...' trigger clause and offers only one concrete action. Adding trigger phrases and a second action verb would lift the completeness and trigger-term scores.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when protecting a PMCC position through an upcoming earnings date or high-risk event.'

Include a second concrete action verb (e.g. 'analyze put duration trade-offs and recommend an optimal protective put') to broaden capability coverage.

Add common synonyms/trigger terms users might say (e.g. 'protective puts', 'earnings hedge', 'LEAPS protection') to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	Names the domain ('tactical collar strategy reports for protecting PMCC positions through earnings or high-risk events') and one concrete action ('Generate ... reports'), but offers only that single action rather than a comprehensive list.	3 / 5
Completeness	The 'what' is clear (generate collar strategy reports), but there is no explicit 'when' trigger clause; the 'through earnings or high-risk events' phrase only weakly implies invocation timing, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes relevant natural terms ('collar', 'PMCC positions', 'earnings', 'high-risk events') that a trader would say, but lacks common synonyms or variations and has no explicit 'Use when' phrasing.	3 / 5
Distinctiveness Conflict Risk	The niche (tactical collars on PMCC positions through earnings) is highly specific and unlikely to trigger for unrelated skills, with only minor overlap risk against other IB/trading skills.	4 / 5
	Total	13 / 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-collar/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.