signals

Signal trading - RSS, Twitter, Telegram triggers to trades

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/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 too terse and lacks the explicit trigger guidance needed for Claude to reliably select this skill. While it names specific platforms and the trading domain, it reads more like a tagline than a functional skill description. The absence of a 'Use when...' clause and limited action specificity significantly weaken its utility for skill selection.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios like 'Use when the user wants to set up automated trades based on social signals, RSS feeds, or messaging alerts'

Expand the action specificity to describe what the skill actually does, e.g., 'Monitors RSS feeds, Twitter accounts, and Telegram channels for trading signals and executes or recommends trades based on configured triggers'

Include additional natural trigger terms users might say such as 'automated trading', 'trade alerts', 'social signals', 'crypto signals', or 'bot trading'

Dimension	Reasoning	Score
Specificity	Names the domain (signal trading) and lists specific trigger sources (RSS, Twitter, Telegram) with an action (trades), but lacks detail on what specific actions are performed beyond 'triggers to trades'.	2 / 3
Completeness	Provides a brief 'what' (signal trading from various sources) but completely lacks a 'Use when...' clause or any explicit guidance on when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant platform names (RSS, Twitter, Telegram) and 'trading' which users might say, but missing common variations like 'crypto', 'automated trading', 'trade signals', 'social trading', or 'alerts'.	2 / 3
Distinctiveness Conflict Risk	The combination of specific platforms (RSS, Twitter, Telegram) with trading creates some distinctiveness, but 'trading' alone could overlap with other trading-related skills, and the description doesn't clearly carve out its niche.	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, concise skill that provides excellent command reference and actionable examples. The main weaknesses are the lack of explicit workflow guidance (e.g., 'first add source, then add filters, then configure amounts, then test before going live') and missing validation/verification steps for what is essentially an automated trading system with real financial risk.

Suggestions

Add a 'Getting Started' workflow section showing the recommended sequence: add source → test detection → add filters → configure amounts → monitor with /signal history before enabling live trades

Include validation steps and error handling guidance, especially for webhook authentication failures, RSS parsing errors, or when trades fail to execute

Add a warning section about risks and recommended safeguards (e.g., start with small amounts, use cooldowns, test filters thoroughly before live trading)

Dimension	Reasoning	Score
Conciseness	Content is lean and efficient with no unnecessary explanations. Every section provides direct, actionable information without explaining what RSS feeds or webhooks are to Claude.	3 / 3
Actionability	Provides complete, copy-paste ready commands with concrete examples. The webhook payload JSON, filter syntax, and configuration options are all specific and executable.	3 / 3
Workflow Clarity	Commands are well-documented but lacks explicit workflow sequencing for the multi-step process of setting up signals and filters. No validation checkpoints or error recovery guidance for what happens when signals fail or trades don't execute.	2 / 3
Progressive Disclosure	Content is reasonably organized into logical sections, but everything is inline in one file. For a feature this complex (multiple signal sources, filters, configuration), advanced topics like sentiment analysis tuning or troubleshooting could be split into separate references.	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.