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.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/claude-code-skills --skill twitter-reader95
Does it follow best practices?
Validation for skill structure
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 an excellent skill description that hits all the key criteria. It clearly specifies what the skill does (fetch Twitter/X content via jina.ai API), when to use it (retrieving tweet content with specific data types), and includes strong trigger terms covering both platform names and common user terminology. The description is concise yet comprehensive.
| 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-crafted, concise skill that provides immediately actionable guidance for fetching Twitter content. The content is efficiently organized with executable examples. The main weakness is the lack of error handling or validation guidance for common failure scenarios (invalid API key, rate limits, deleted tweets).
Suggestions
Add a brief troubleshooting section covering common errors (401 unauthorized, rate limits, 404 for deleted tweets) and how to handle them
| 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 | For a simple fetch operation, the steps are clear. However, there's no error handling guidance or validation steps (e.g., what to do if API key is invalid, rate limits hit, or tweet not found). | 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 deep 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.
Table of Contents
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.