twitter-reader
Fetch Twitter/X post content by URL using jina.ai API to bypass JavaScript restrictions. Use when Claude needs to retrieve tweet content including author, timestamp, post text, images, and thread replies. Supports individual posts or batch fetching from x.com or twitter.com URLs.
92
93%
Does it follow best practices?
Impact
81%
1.06xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a well-crafted skill description that excels across all dimensions. It clearly specifies the capability (fetching Twitter/X content via jina.ai), includes comprehensive trigger terms covering both platform names and content types, and has an explicit 'Use when' clause. The description is distinctive enough to avoid conflicts with general web scraping skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Fetch Twitter/X post content', 'retrieve tweet content including author, timestamp, post text, images, and thread replies', 'individual posts or batch fetching'. Clear technical approach mentioned (jina.ai API). | 3 / 3 |
Completeness | Clearly answers both what ('Fetch Twitter/X post content by URL using jina.ai API') and when ('Use when Claude needs to retrieve tweet content including author, timestamp, post text, images, and thread replies'). Explicit 'Use when' clause present. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Twitter', 'X', 'post', 'tweet', 'x.com', 'twitter.com', 'URLs', 'thread', 'replies'. Covers both old and new platform names. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Twitter/X content retrieval. The specific platform names, URL patterns (x.com, twitter.com), and content types (tweets, threads) make it highly distinguishable from other web scraping or social media skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that provides immediately actionable guidance for fetching Twitter content. The content respects Claude's intelligence and provides executable examples. The main weakness is the lack of error handling or validation guidance for when API calls fail or return unexpected results.
Suggestions
Add a brief troubleshooting section covering common failure modes (invalid API key, rate limits, deleted tweets) and how to handle them
Include example output showing what the returned markdown content looks like so Claude knows what to expect
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient. No unnecessary explanations of what Twitter is or how APIs work. Every section serves a purpose with minimal padding. | 3 / 3 |
Actionability | Provides fully executable curl commands and script invocations that are copy-paste ready. Clear examples with actual command syntax and placeholder values. | 3 / 3 |
Workflow Clarity | Steps are clear for the simple use case, but lacks validation/error handling guidance. No mention of what to do if API calls fail, rate limits hit, or invalid URLs provided. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections. Quick start for immediate use, then details on scripts and URL formats. References bundled scripts appropriately without over-nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- daymade/claude-code-skills
- Commit
392d34c
- 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.