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.
85
82%
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 an excellent skill description that clearly communicates what the skill does, when to use it, and includes strong natural trigger terms. It specifies concrete capabilities (author, timestamp, text, images, thread replies), provides explicit 'Use when' guidance, and occupies a distinct niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: fetch post content by URL, retrieve author/timestamp/post text/images/thread replies, supports individual posts or batch fetching. Also specifies the mechanism (jina.ai API) and the reason (bypass JavaScript restrictions). | 3 / 3 |
Completeness | Clearly answers both what ('Fetch Twitter/X post content by URL using jina.ai API...including author, timestamp, post text, images, and thread replies') and when ('Use when Claude needs to retrieve tweet content...from x.com or twitter.com URLs'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Twitter', 'X', 'tweet', 'post', 'x.com', 'twitter.com', 'URL'. These are all terms a user would naturally use when requesting tweet content retrieval. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Twitter/X content fetching via specific API. The platform-specific triggers (x.com, twitter.com, tweet) and the specific tool (jina.ai) make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid, actionable skill with clear executable examples for fetching tweets via Jina API. Main weaknesses are the lack of error handling/validation guidance (especially important for batch operations and API authentication) and some minor verbosity in sections that describe things Claude would already understand. The structure is clean but could better leverage progressive disclosure by linking to script files.
Suggestions
Add error handling guidance: what to check if the API returns errors (invalid key, rate limits, deleted tweets), especially for batch operations where partial failures are likely.
Remove or condense the 'What Gets Returned' section—Claude can parse the response directly; instead, show a brief example of actual output.
Link to the actual script files (e.g., [fetch_tweet.py](scripts/fetch_tweet.py)) so Claude can inspect implementation details without cluttering the main skill file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary sections like 'What Gets Returned' which describes fairly obvious API response fields, and the 'URL Formats Supported' section is somewhat redundant given the examples already show the URL pattern. The prerequisites section explaining how to sign up is borderline unnecessary for Claude. | 2 / 3 |
Actionability | Provides fully executable curl commands and script invocations with clear syntax. The quick start curl example is copy-paste ready, and the bundled script usage is concrete with specific command-line arguments. | 3 / 3 |
Workflow Clarity | The skill presents clear steps for single and batch fetching, but lacks any validation or error handling guidance. There's no mention of what to do if the API key is invalid, if rate limits are hit, or if a tweet URL returns an error. For batch operations, missing feedback loops cap this at 2. | 2 / 3 |
Progressive Disclosure | References bundled scripts (fetch_tweet.py, fetch_tweets.sh) but doesn't link to their source or any additional documentation. The content is reasonably organized with clear sections, but the scripts section could benefit from linking to the actual script files for details rather than repeating usage inline. | 2 / 3 |
Total | 9 / 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.
4f0eae8
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.