signals

Signal trading - RSS, Twitter, Telegram triggers to trades

Quality

42%

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/signals/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 is a terse fragment that conveys the general domain—converting signals from social/feed sources into trades—but lacks concrete action verbs, explicit trigger guidance, and sufficient detail for reliable skill selection. It reads more like a tagline than a functional description, leaving Claude without clear criteria for when to choose this skill over others.

Suggestions

Add an explicit 'Use when...' clause listing trigger scenarios, e.g., 'Use when the user wants to set up automated trading based on RSS feeds, Twitter posts, or Telegram channel signals.'

Expand with specific concrete actions such as 'Parses trading signals from RSS feeds, Twitter accounts, and Telegram channels, maps them to buy/sell orders, and executes trades via exchange APIs.'

Include additional natural trigger terms users might say, such as 'automated trading', 'trade bot', 'copy trading', 'signal alerts', or 'social trading'.

Dimension	Reasoning	Score
Specificity	Names the domain (signal trading) and lists some input sources (RSS, Twitter, Telegram) and the output (trades), but doesn't describe concrete actions like parsing signals, placing orders, configuring triggers, or managing positions.	2 / 3
Completeness	Provides a brief 'what' (signal trading from RSS/Twitter/Telegram to trades) 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' itself is also quite thin, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'RSS', 'Twitter', 'Telegram', 'trading', and 'triggers' that users might naturally say, but misses common variations like 'trade signals', 'automated trading', 'bot', 'alerts', 'crypto signals', or 'copy trading'.	2 / 3
Distinctiveness Conflict Risk	The combination of signal sources (RSS, Twitter, Telegram) with trading is somewhat distinctive, but 'trading' alone is broad and could overlap with other trading-related skills. The description doesn't clearly carve out its niche versus general trading bots or social media monitoring skills.	2 / 3
	Total	7 / 12 Passed

Implementation

52%

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

The skill is concise and well-structured as a command reference, but it reads more like API documentation than an actionable skill. It critically lacks a workflow showing the end-to-end process of setting up signal-triggered trading, with no validation steps or safety checks for what is essentially an automated financial operation. The absence of error handling, testing workflows, and verification steps is a significant gap for a skill involving real money.

Suggestions

Add a step-by-step workflow section (e.g., '## Getting Started Workflow') that sequences: add source → configure filters → set trade amounts → test with /signal test → verify with paper trade → enable live trading, with explicit validation at each step.

Include validation and safety checkpoints: verify signal source is receiving data before adding filters, test filters with /signal test before enabling live trades, and add a dry-run/paper-trade mode recommendation.

Add error handling guidance: what happens when a signal source goes down, when a trade fails, or when filters match unexpectedly. Include recovery steps for each scenario.

Consider linking to separate reference files for advanced topics like sentiment analysis configuration, routing details (Pump.fun/Raydium/Jupiter), and P&L tracking setup.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It doesn't explain what RSS feeds or webhooks are, assumes Claude's competence, and every section delivers actionable information without padding.	3 / 3
Actionability	Commands and examples are concrete and copy-paste ready, but this is a command reference rather than executable code. There's no implementation detail—no code showing how signals are actually processed, how filters are evaluated, or how trades are executed. The commands describe an interface but lack the backing logic.	2 / 3
Workflow Clarity	There is no clear workflow sequence for the multi-step process of setting up signal-to-trade automation. Steps like 'add source → configure filters → set trade parameters → test → monitor' are never laid out as a workflow. For a system that triggers automatic trades (a destructive/financial operation), there are no validation checkpoints, no error recovery steps, and no verification that a signal source is working before enabling live trading.	1 / 3
Progressive Disclosure	The content is reasonably well-organized with clear section headers (Commands, Signal Sources, Filters, Configuration), but everything is in a single file with no references to deeper documentation. The Features section is a bullet list that could link to detailed docs on routing, sentiment analysis, or P&L tracking.	2 / 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.