positions

Position management with stop-loss, take-profit, and trailing stops

Quality

45%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/positions/SKILL.md

Quality

Discovery

32%

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 identifies a clear trading domain and names key order types, providing moderate specificity. However, it lacks a 'Use when...' clause, doesn't enumerate concrete operations beyond listing order types, and misses common trigger term variations. It reads more like a feature label than a skill description that would help Claude reliably select it from a large skill set.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about managing open positions, setting stop-loss or take-profit levels, or configuring trailing stops for trades.'

Expand trigger terms to include common variations like 'SL', 'TP', 'exit strategy', 'risk management', 'trade exits', and 'order management'.

List specific concrete actions such as 'Sets stop-loss and take-profit prices, adjusts trailing stop distances, monitors open positions for exit conditions, and calculates risk-reward ratios.'

Dimension	Reasoning	Score
Specificity	Names the domain (position management) and lists some specific actions (stop-loss, take-profit, trailing stops), but doesn't elaborate on what concrete operations are performed—e.g., setting, modifying, monitoring, or executing these orders.	2 / 3
Completeness	Describes what the skill does (position management with specific order types) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only partially described, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant trading keywords like 'stop-loss', 'take-profit', and 'trailing stops' that users might naturally say, but misses common variations such as 'SL', 'TP', 'exit strategy', 'risk management', 'order management', or 'trade management'.	2 / 3
Distinctiveness Conflict Risk	The mention of stop-loss, take-profit, and trailing stops narrows the domain to trading/position management, which is somewhat distinctive, but 'position management' could overlap with portfolio management or general trading skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

57%

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

The skill excels at actionability with concrete, executable TypeScript examples and clear chat command syntax. However, it suffers from being a monolithic reference document rather than a well-structured skill overview—the full API reference should be split into a separate file. It also lacks workflow guidance for the position management lifecycle and error handling/validation steps for what are essentially financial operations with real consequences.

Suggestions

Split the TypeScript API reference into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with quick-start examples and links to the detailed reference.

Add a workflow section showing the typical position management lifecycle: open position → set initial stops → monitor → handle triggered stops → review execution, with validation at each step.

Add error handling guidance: what happens if a stop-loss order fails to execute, if a position is closed before a stop triggers, or if price gaps past the stop level.

Remove the 'Stop Types' table and 'Order Execution' table—these explain basic trading concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good code examples, but includes some unnecessary elements like the 'Stop Types' table explaining what stop-loss and take-profit are (concepts Claude already knows), and the 'Best Practices' section is generic trading advice rather than skill-specific guidance. The API reference section is quite long and could benefit from being split into a separate file.	2 / 3
Actionability	The skill provides fully executable TypeScript code examples with concrete parameters, specific chat commands with clear syntax, and multiple usage patterns (absolute price, percentage, partial exits). All examples are copy-paste ready with realistic values.	3 / 3
Workflow Clarity	While individual operations are clear, there's no explicit workflow for the overall position management lifecycle (e.g., create position → set stops → monitor → handle triggers). There are no validation checkpoints—for instance, no guidance on verifying a stop was actually set, handling failed order execution, or what to do if the position no longer exists when a stop triggers.	2 / 3
Progressive Disclosure	This is a monolithic wall of content—the full API reference, chat commands, event handlers, and best practices are all inline in a single file. The extensive TypeScript API reference (which dominates the file) should be in a separate REFERENCE.md, with SKILL.md serving as a concise overview with links.	1 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: e71a5f6

Reviewed: 11 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.