twitter-reader

Fetch Twitter/X post content including long-form Articles with full images and metadata. Use when Claude needs to retrieve tweet/article content, author info, engagement metrics, and embedded media. Supports individual posts and X Articles (long-form content). Automatically downloads all images to local attachments folder and generates complete Markdown with proper image references. Preferred over Jina for X Articles with images.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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 body is highly actionable with executable commands and verified script references, but suffers from redundant sections and lacks validation checkpoints in its batch workflow. Inline descriptive content could be split out for better progressive disclosure.

Suggestions

Dedupe the fetch_article.py command — keep it once in Quick Start and reference it from the Scripts/Migration sections instead of repeating the full invocation.

Consolidate the overlapping "Example Output", "Output Structure", and "What Gets Returned" sections into a single concise output description.

Add a validation/verification step for the batch fetch_tweets.sh workflow (e.g., check each output file exists and report failures) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	Avoids explaining concepts Claude already knows, but is padded with redundancy: the same fetch_article.py command appears in Quick Start, Scripts, and Migration sections, and "Example Output", "Output Structure", "What Gets Returned", and "Features" overlap significantly. Not a 3 because the repetition could be tightened; not a 1 because there is no concept-explanation fluff.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands ("uv run --with pyyaml python scripts/fetch_article.py <article_url> [output_dir]", curl with JINA_API_KEY, "scripts/fetch_tweets.sh url1 url2 url3") with concrete examples matching the executable anchor.	3 / 3
Workflow Clarity	The "This will:" list sequences the script's internal steps, but there are no explicit validation/verification checkpoints, and the batch fetch_tweets.sh workflow lacks any error-recovery loop — capping workflow clarity at 2 per the batch-operations guideline. Not a 1 because a sequence is present.	2 / 3
Progressive Disclosure	Scripts (fetch_article.py, fetch_tweet.py, fetch_tweets.sh) are referenced one level deep and verified to exist in scripts/, but all descriptive content (example output, output structure, features, migration) is inline in a single ~150-line SKILL.md with no separate reference docs. Some structure, but content that could be split is inline — a 2 rather than 3.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 strong, specific description that clearly answers both what the skill does and when to use it, with natural trigger terms and a distinct niche. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Fetch Twitter/X post content", "retrieve tweet/article content, author info, engagement metrics, and embedded media", "Automatically downloads all images", "generates complete Markdown" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly states both what it does and when to use it via "Use when Claude needs to retrieve tweet/article content…", in proper third-person voice.	3 / 3
Trigger Term Quality	Covers natural terms a user would say ("Twitter/X post", "tweet/article", "author info", "engagement metrics", "embedded media", "images") with good variation, not just jargon.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (Twitter/X content fetching) with distinct triggers and an explicit "Preferred over Jina for X Articles with images" differentiator, unlikely to conflict with unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: daymade/claude-code-skills
Commit: e5ac7ba

Reviewed: about 6 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.