CtrlK
BlogDocsLog inGet started
Tessl Logo

social-media-intelligence

Social media intelligence: financial signal extraction from Twitter/X, Telegram, Discord, and Reddit for sentiment-driven trading strategies.

51

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/social-media-intelligence/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable with extensive executable code and clear section organization, but it is a monolithic, always-loaded ~1290-line document that lacks progressive disclosure into reference files and omits explicit validation feedback loops for its batch collection workflows.

Suggestions

Split the body into one-level-deep reference files (e.g. references/data-collection.md, references/sentiment-methods.md, references/factor-construction.md, references/platform-analysis.md) and keep SKILL.md as a concise overview that links to them, improving both conciseness and progressive disclosure.

Trim Section 1's platform/role/subreddit/channel tables and shorten the per-function docstrings to assume Claude's knowledge of these platforms, cutting the always-loaded token cost.

Add explicit validation/retry checkpoints for batch collection (e.g. verify rate-limit headers, validate schema on ingest, retry-on-failure with backoff, confirm purge of >30-day raw data) to lift workflow clarity above 2.

DimensionReasoningScore

Conciseness

Most of the quant methodology (IC/ICIR, orthogonalization, fear/greed, platform weights) is specialized and earns its place, but the ~1290-line monolithic body loads fully into context and pads Section 1 with platform/role/subreddit/channel tables and verbose per-function docstrings Claude could largely do without, matching 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean anchor above.

2 / 3

Actionability

The body is packed with concrete, executable Python across tweepy, telethon, discord.py, praw, VADER, FinBERT, pandas, scipy and sklearn, plus JSON schemas, env vars and SQL DDL that are largely copy-paste ready, matching the 'fully executable code/commands; specific examples' anchor; the few undefined helpers (_collect_twitter, get_llm) are minor stubs rather than pseudocode.

3 / 3

Workflow Clarity

The seven numbered sections give a clear logical progression and include useful checklist tables (IC/ICIR grading, WSB short-squeeze checklist, fear/greed thresholds), but there are no explicit validate->fix->retry feedback loops for the batch collection and destructive data-purge operations, which per the guidelines caps workflow clarity at 2.

2 / 3

Progressive Disclosure

Sections are well-organized internally, but the skill is a single monolithic ~1290-line SKILL.md with no references/scripts/assets bundle and no one-level-deep file references; platform-specific analysis, data schemas and factor methodology that should be separate files are all inline, matching 'some structure but content that should be separate is inline' rather than the well-split anchor above.

2 / 3

Total

9

/

12

Passed

Description

50%

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 names a clear domain and concrete platforms but reads as a single declarative jargon-heavy clause with no 'Use when' trigger guidance and only one core action, leaving it undifferentiated from the reader skills it builds on.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building sentiment-driven trading factors from social media data or when the user mentions Twitter/Telegram/Discord/Reddit sentiment for trading.'

Expand the action list from the single verb 'extraction' to concrete capabilities like 'collect, score sentiment, build buzz and fear/greed metrics, and test IC/ICIR of social-sentiment factors'.

Soften the jargon with natural terms a user would say ('analyze social media sentiment', 'social trading signals') to improve trigger-term quality.

DimensionReasoningScore

Specificity

The description names the domain and four concrete platforms ('financial signal extraction from Twitter/X, Telegram, Discord, and Reddit') but lists only one core action (extraction) rather than multiple distinct concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multiple-action anchor above.

2 / 3

Completeness

It clearly states what the skill does (financial signal extraction across platforms for trading strategies) but includes no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Platform names (Twitter/X, Telegram, Discord, Reddit) and 'sentiment'/'trading strategies' are relevant keywords a user might say, but the phrasing ('financial signal extraction', 'sentiment-driven trading strategies') is formal jargon that misses more natural conversational variations like 'analyze social media sentiment for trading', so it sits at 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The 'sentiment-driven trading strategies' niche is fairly specific, but the skill explicitly draws on separate twitter-reader/telegram-reader/discord-reader modules and lacks a trigger clause to disambiguate, so a 'read Telegram messages' request could still overlap with those reader skills, matching 'somewhat specific but could still overlap'.

2 / 3

Total

8

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1296 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
HKUDS/Vibe-Trading
Reviewed

Table of Contents

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.