CtrlK
BlogDocsLog inGet started
Tessl Logo

social-data

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

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 an excellent, lean, copy-paste-ready reference: every section is an executable curl command with the right headers and query operators, and there is no filler. The only weakness is minor: with no bundle files, all API detail is inlined rather than split into one-level-deep references.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with no padding explaining what an API or JSON endpoint is; every curl example and parameter note earns its place, matching the 5-anchor for token efficiency.

5 / 5

Actionability

All examples are copy-paste-ready curl commands with real URLs, required headers, and enumerated query operators across the three platforms, matching the 5-anchor for fully executable guidance.

5 / 5

Workflow Clarity

Each section describes a single, unambiguous fetch action and the skill is read-only (not destructive or batch), so the simple-skill exception applies and the actions are crystal clear; no validation checkpoints are needed for GET lookups.

5 / 5

Progressive Disclosure

Content is cleanly sectioned per platform and per endpoint type with no nested references, but the body exceeds 50 lines and inlines API-reference detail with no one-level-deep references to separate files, placing it just below the 5-anchor.

4 / 5

Total

19

/

20

Passed

Description

70%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 clearly communicates what the skill does and across which platforms, with strong distinctiveness and good natural keywords. Its main weakness is the complete absence of a "Use when..." trigger clause, which caps its completeness score.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases (e.g., 'Use when the user asks to pull tweets, Reddit posts, or Hacker News stories.') to lift completeness above 3.

Broaden trigger terms with common synonyms such as 'tweets', 'posts', 'subreddit', and 'HN'.

Add one or two more concrete verbs (e.g., 'list', 'browse') to round out the action vocabulary toward a 5 on specificity.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Search and fetch") across three named platforms, but the verb set is limited rather than comprehensive, sitting above the 3-anchor's 1-2 actions and below the 5-anchor's full coverage.

4 / 5

Completeness

The "what" is clearly stated (search and fetch social media data from three platforms) but there is no "Use when..." or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Natural platform terms ("Twitter/X", "Reddit", "Hacker News", "social media") give good keyword coverage, though common synonyms like "tweets", "posts", "subreddit", and "HN" are missing.

4 / 5

Distinctiveness Conflict Risk

Naming three specific platforms carves out a clear niche with distinct triggers and minimal overlap risk, matching the 5-anchor.

5 / 5

Total

16

/

20

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

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
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.