CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

x-twitter-scraper

X (Twitter) data platform skill — tweet search, user lookup, follower extraction, engagement metrics, giveaway draws, monitoring, webhooks, 19 extraction tools, MCP server.

Quality

76%

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 ./skills/x-twitter-scraper/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, well-structured overview with executable setup commands and a clear capability map, but it stops short of showing how to actually invoke the API: there is no sample request and no step-by-step workflow for the batch extraction and monitoring operations the skill centers on. Adding a worked API call example and an extraction workflow with polling/validation would address the weakest dimensions.

Suggestions

Add a copy-paste-ready sample request, e.g. a curl call to /x/tweets/search with the x-api-key header and a representative JSON response, so the API reference is directly actionable.

Document the bulk-extraction workflow end to end (POST /extractions → poll status → verify results, using /extractions/estimate up front) with validation checkpoints to lift workflow clarity past the batch-operation cap.

Consolidate the capability lists repeated across Overview, When to Use, and the Capabilities table into one authoritative section to trim duplicate tokens.

DimensionReasoningScore

Conciseness

The body is efficient — compact tables, no explanations of concepts Claude already knows — but capability listings are repeated across the Overview, "When to Use This Skill", and the Capabilities table, and the 19 tools are enumerated twice, so a few tokens could be trimmed. It is not a 5 because of this duplication, and not a 3 since there is no padding or unnecessary explanation.

4 / 5

Actionability

Concrete executable guidance is present ("npx skills add Xquik-dev/x-twitter-scraper", "export XQUIK_API_KEY=...", base URL, auth header, full endpoint table with methods), but there is no sample API request or response showing how to actually call an endpoint, leaving a minor gap. Not a 3 because the commands given are genuinely executable rather than pseudocode.

4 / 5

Workflow Clarity

Setup is clearly sequenced (install → get key → export), but operational workflows like bulk extraction and monitoring are not sequenced (no start → poll → verify steps) and validation/verification steps are absent. Since the skill includes batch operations ("19 Extraction Tools", "/extractions"), the batch-operation cap limits workflow clarity to 3; it is above 2 because setup steps and an endpoint map do exist.

3 / 5

Progressive Disclosure

The single file is well-organized into clear sections (Overview, When to Use, Setup, Capabilities, Examples, API Reference) with no nested references and no buried content. It is not a 5 because the file exceeds 50 lines and the API reference table is a candidate for a separate reference file, but structure and placement are otherwise good.

4 / 5

Total

15

/

20

Passed

Description

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

A specific, capability-dense description in third person with a well-defined niche. Its main weakness is the complete absence of "when to use" trigger guidance, which caps completeness; adding a "Use when..." clause covering the natural user phrasings would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about tweets, X/Twitter profiles, follower lists, engagement metrics, trending topics, or giveaway draws" to fix the missing 'when' and unlock a higher completeness score.

Include commonly-spoken variations such as "trending topics", "scrape tweets", and "check who follows whom" to broaden natural trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists nine concrete actions ("tweet search, user lookup, follower extraction, engagement metrics, giveaway draws, monitoring, webhooks, 19 extraction tools, MCP server") with comprehensive coverage and no gaps, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

The "what" is clearly and concretely stated, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; the "when" is entirely absent rather than merely imprecise, so it cannot score 4.

3 / 5

Trigger Term Quality

Natural terms like "tweet search", "follower", "engagement metrics", and "X (Twitter)" cover the main phrasings users would say, but common variations such as "trending", "scrape tweets", or "giveaway winner" are missing, placing it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear X/Twitter data niche with distinct triggers (tweets, followers, giveaways, monitoring, webhooks) that are unlikely to collide with other skills, matching the minimal-conflict anchor.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/x-twitter-scraper/SKILL.md

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.