social-data

Search and fetch social media data from Twitter/X, Reddit, and Hacker News.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/social-data/SKILL.md

Quality

Content

82%Weight 40%Scale 1-5

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

The body is a highly actionable, token-efficient API reference: executable curl examples with required auth headers and response shapes for every endpoint across all three platforms. Its weaknesses are minor — a time-sensitive Twitter tier claim, an implicit USER_ID dependency in the timeline flow, and no error-handling guidance.

Suggestions

Remove or date-stamp the "Twitter free tier allows 500K tweets/month read access" claim, since quota tiers change and it is not in a deprecated section.

Make the Twitter timeline flow explicit: note that USER_ID comes from the user-lookup endpoint response before calling /2/users/USER_ID/tweets.

Add a brief note on handling 401/429 responses (e.g. checking rate-limit headers) for the APIs used.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-first with almost no padding (e.g. "Query operators:", "Response is array of two listings: [0] = post, [1] = comments tree"), but the time-sensitive claim "Twitter free tier allows 500K tweets/month read access" is not placed in a deprecated/old-patterns section, keeping it just below the lean-and-efficient anchor.	4 / 5
Actionability	Every section provides a copy-paste-ready curl command with required headers ("User-Agent: bitterbot/1.0", "Authorization: Bearer $TWITTER_BEARER_TOKEN"), the needed env var is named, and response shapes and query operators are documented across all common cases per platform.	5 / 5
Workflow Clarity	Each operation is a self-contained read-only command, well organized by platform, so no destructive-operation validation is needed; however the Twitter timeline depends on a USER_ID only implicitly obtainable from the user-lookup endpoint, and there is no guidance for handling 401/429 responses.	4 / 5
Progressive Disclosure	Content is tightly organized under clear per-platform and per-operation headers with everything appropriately inline for its size, but at roughly 118 lines it exceeds the under-50-line simple-skill case and keeps all API reference (e.g. the full query-operator list) inline rather than splitting it out.	4 / 5
	Total	17 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 concise, third-person, and anchored by concrete platform names that serve as strong trigger terms, but it undersells the skill's actual capabilities and omits any "Use when..." guidance, capping both specificity and completeness. Adding an explicit trigger clause and one or two more concrete actions would raise it substantially.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks about tweets, Reddit posts, HN stories, or social media trends.'

List a few more concrete actions to match the skill's coverage, e.g. 'Search and fetch social media data (top stories, posts, comments, user profiles) from Twitter/X, Reddit, and Hacker News.'

Include common synonyms users say, such as 'tweets', 'HN', and 'subreddit', to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	"Search and fetch social media data" names the domain and exactly two concrete actions, matching the 1-2-actions anchor; it does not list the several specific capabilities it actually covers (trending stories, comments, user timelines).	3 / 5
Completeness	The "what" is clear (search and fetch social data from three named platforms), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	"Twitter/X", "Reddit", and "Hacker News" are precisely the platform names a user would naturally say, but common variations like "tweets", "posts", "HN", or "subreddit" are missing, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Naming three specific platforms carves out a clear niche with only minor overlap risk against generic web-search/scraping skills; it is not a 5 because "social media data" remains a fairly broad scope.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: Bitterbot-AI/bitterbot-desktop
Path: skills/social-data/SKILL.md
Commit: 1c7dc1b

Reviewed: 20 hours 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.