Search and retrieve content from Twitter/X. Get user info, tweets, replies, followers, communities, spaces, and trends via twitterapi.io. Use when user mentions Twitter, X, or tweets.
92
96%
Does it follow best practices?
Impact
73%
5.61xAverage 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 strong skill description that concisely lists specific capabilities, names the data source (twitterapi.io), and includes an explicit 'Use when' clause with natural trigger terms. It covers both platform name variations (Twitter/X) and enumerates the types of content retrievable. The description is well-structured and would perform well in a multi-skill selection scenario.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Get user info, tweets, replies, followers, communities, spaces, and trends' — these are distinct, enumerated capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Search and retrieve content from Twitter/X. Get user info, tweets, replies, followers, communities, spaces, and trends via twitterapi.io') and when ('Use when user mentions Twitter, X, or tweets') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Twitter', 'X', 'tweets', plus domain-specific terms like 'followers', 'replies', 'trends', 'spaces', 'communities'. Covers the platform name variation (Twitter/X). | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche — Twitter/X content retrieval via a specific API (twitterapi.io). The platform-specific triggers (Twitter, X, tweets) are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides clear, actionable commands for Twitter/X data retrieval. It's concise, assumes Claude's competence, and organizes endpoints logically by category. The main weakness is the lack of bundle files to verify script existence and the absence of output format documentation that would help Claude process responses.
Suggestions
Add brief example output (or reference to an OUTPUTS.md) showing the JSON structure returned by at least one command, so Claude knows how to parse and present results to users.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows how to run Python scripts and use environment variables. Every section serves a clear purpose with no unnecessary explanation of what Twitter is or how APIs work. | 3 / 3 |
Actionability | Every command is fully concrete and copy-paste ready with clear argument patterns. The search query syntax section provides specific, executable examples covering common use cases. The prerequisite setup is explicit. | 3 / 3 |
Workflow Clarity | This is a simple retrieval skill (read-only, non-destructive) where each command is a single action. The prerequisite check provides a validation step. No multi-step destructive workflows exist that would require feedback loops, so the clear command listing is sufficient. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers grouping related endpoints. However, no bundle files were provided to verify the referenced scripts exist, and the skill could benefit from referencing external docs for advanced usage or output format details rather than keeping everything inline. | 2 / 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.
74fa178
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.