ib-trailing-stop

Server-side trailing stop management for stocks and naked LEAPS in IB. Places native TRAIL orders that auto-ratchet the stop as price climbs. Dry-run by default. Requires TWS or IB Gateway running locally.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/ib-trailing-stop/SKILL.md

Quality

Content

76%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 lean, highly actionable, and well-structured with a real script bundle backing the commands. Its main weakness is the destructive execute workflow, which relies on the dry-run default rather than an explicit validation/confirmation checkpoint before placing live orders.

Suggestions

Add an explicit validation checkpoint between dry-run and execute — e.g. 'Show the dry-run report, confirm with the user, then re-run with --execute' — to satisfy the destructive/batch feedback-loop requirement.

Consider moving the full JSON output structure and the architecture function listing into a short reference file, keeping SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	Efficient and assumes Claude's competence — no padding or basic-concept explanations — though the inline JSON output block and architecture function listing could be trimmed slightly.	4 / 5
Actionability	Fully executable, copy-paste-ready commands covering dry-run, execute, and forced modes (e.g. 'uv run python .claude/skills/ib-trailing-stop/scripts/trailing_stop.py --symbols JOBY --trail-pct 20 --execute'), with a complete arguments table and concrete JSON output schema.	5 / 5
Workflow Clarity	A clear three-step sequence exists (run script, format report, report to user) and dry-run-by-default is an implicit safety checkpoint, but the destructive/batch execute path lacks explicit validation checkpoints or a verify-then-execute feedback loop, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized into clearly headed sections with the executable logic correctly split into the bundled scripts/trailing_stop.py (the path referenced in the commands is a real bundle file) and no nested reference chains; minor organization gaps only.	4 / 5
	Total	16 / 20 Passed

Description

66%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 well-scoped with strong natural trigger terms, but it omits an explicit 'Use when' clause, which caps its completeness. Distinctiveness is good though it borders on a sibling skill's territory.

Suggestions

Add an explicit 'Use when...' clause naming the trigger phrases users would say (e.g. 'Use when the user wants to set trailing stops on stock or naked LEAPS positions in IB').

Clarify the boundary against ib-stop-loss in the description itself (e.g. 'For PMCC positions use ib-stop-loss instead') rather than only in the body.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Places native TRAIL orders that auto-ratchet the stop as price climbs', 'Dry-run by default', 'Requires TWS or IB Gateway running locally' — with only minor coverage gaps.	4 / 5
Completeness	The 'what' is clear (server-side trailing stop management for stocks and naked LEAPS) but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Good natural keyword coverage for the audience — 'trailing stop', 'stocks', 'naked LEAPS', 'IB', 'TRAIL orders', 'TWS', 'IB Gateway' — with a few common synonyms absent.	4 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche (trailing stops on stocks and naked LEAPS in IB) with mostly distinct triggers, but minor overlap risk with the closely related ib-stop-loss skill noted in the body.	4 / 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-trailing-stop/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.