positions

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

Quality

56%

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 with specific feature terminology but fails to explain what actions the skill performs or when Claude should use it. It reads more like a feature list than an actionable skill description, lacking both concrete verbs and explicit trigger conditions.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to set stop-loss orders, configure take-profit levels, or manage trailing stops on trading positions'

Include concrete action verbs describing what the skill does: 'Sets and monitors stop-loss orders, configures take-profit targets, manages trailing stop adjustments'

Add common user terminology variations: 'SL', 'TP', 'exit orders', 'risk management', 'position exits'

Dimension	Reasoning	Score
Specificity	Names the domain (position management) and lists specific features (stop-loss, take-profit, trailing stops), but doesn't describe concrete actions like 'set', 'modify', 'calculate', or 'monitor'.	2 / 3
Completeness	Describes what features exist but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant trading terms (stop-loss, take-profit, trailing stops) that users might say, but misses common variations like 'SL', 'TP', 'exit strategy', 'risk management', or 'close position'.	2 / 3
Distinctiveness Conflict Risk	The trading-specific terms provide some distinction, but 'position management' is broad enough to potentially overlap with portfolio management or general trading skills.	2 / 3
	Total	7 / 12 Passed

Implementation

79%

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

This is a well-structured API reference with excellent actionability and conciseness. The code examples are complete and executable, and the content respects Claude's intelligence by avoiding unnecessary explanations. However, it lacks explicit workflow guidance for common scenarios (e.g., setting up a new position with stops) and could benefit from progressive disclosure by splitting into multiple files.

Suggestions

Add a workflow section showing the complete flow: create position → set stops → monitor → handle triggers, with explicit validation steps

Include error handling examples showing what happens when stop execution fails and how to recover

Consider splitting into SKILL.md (overview + quick start), COMMANDS.md (chat commands), and API.md (TypeScript reference)

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, presenting API reference material without unnecessary explanations. Every section provides direct, actionable information without explaining what stop-losses or positions are conceptually.	3 / 3
Actionability	Provides fully executable TypeScript code examples that are copy-paste ready, with concrete chat commands and complete API usage patterns including all parameter options.	3 / 3
Workflow Clarity	While individual operations are clear, there's no explicit workflow for setting up position management end-to-end. The 'Best Practices' section lists guidelines but lacks validation checkpoints or error recovery steps for when stops fail to execute.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but this is a monolithic 200+ line file that could benefit from splitting API reference, chat commands, and best practices into separate files with a concise overview in the main skill.	2 / 3
	Total	10 / 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: 2a8c94e

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