features

Real-time market features and trading signals

Quality

30%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague and incomplete to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient detail to distinguish it from other potential market or data analysis skills. The description reads more like a category label than a functional skill description.

Suggestions

Add specific concrete actions using verbs (e.g., 'Generates buy/sell signals, calculates technical indicators, monitors price movements, analyzes market trends')

Include a 'Use when...' clause with explicit triggers (e.g., 'Use when the user asks about stock prices, trading recommendations, technical analysis, or market indicators')

Add natural trigger terms users would say (e.g., 'stocks, crypto, RSI, moving averages, buy signal, sell signal, price alerts, market analysis')

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('real-time market features', 'trading signals') without listing any concrete actions. It doesn't specify what operations can be performed - no verbs describing capabilities.	1 / 3
Completeness	Missing both clear 'what' (no specific actions described) and 'when' (no 'Use when...' clause or trigger guidance). The description only vaguely hints at a domain without explaining capabilities or usage triggers.	1 / 3
Trigger Term Quality	Contains some relevant domain keywords ('market', 'trading signals') that users might mention, but lacks common variations like 'stocks', 'crypto', 'buy/sell', 'technical analysis', 'indicators', or specific signal types.	2 / 3
Distinctiveness Conflict Risk	The 'trading signals' term provides some specificity to the financial domain, but 'market features' is generic enough to potentially conflict with other finance, analytics, or data skills.	2 / 3
	Total	6 / 12 Passed

Implementation

37%

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

This skill is extremely minimal - essentially just a command reference without actionable guidance. While concise, it fails to provide concrete examples of command usage, expected output formats, or any workflow for interpreting trading signals. A user would not know what features are computed, what signals mean, or how to act on the information.

Suggestions

Add concrete examples showing command usage with sample output (e.g., what does `/features get polymarket 12345` return?)

Document what specific features and signals are computed and what they mean for trading decisions

Include a basic workflow: how to identify markets, get features, interpret signals, and validate recommendations

Add parameter format details (what is a valid platform name? what format is marketId?)

Dimension	Reasoning	Score
Conciseness	The content is extremely lean - just a brief description and command reference. No unnecessary explanations or padding.	3 / 3
Actionability	Only lists command syntax without any concrete examples of usage, expected outputs, parameter formats, or what the features/signals actually contain. No executable guidance.	1 / 3
Workflow Clarity	No workflow is described. Commands are listed but there's no guidance on when to use each, how they relate, or any validation/verification steps for trading decisions.	1 / 3
Progressive Disclosure	Content is brief and organized with clear sections, but lacks any references to detailed documentation for the trading signals, feature definitions, or advanced usage.	2 / 3
	Total	7 / 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: 28 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.