A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.
86
82%
Does it follow best practices?
Impact
97%
1.44xAverage 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 clearly identifies the tool's purpose, lists comprehensive concrete actions, and includes an explicit 'Use this skill when...' clause with natural trigger terms. It covers both the platform names (X and Twitter) and a wide range of specific operations, making it easy for Claude to select appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, and interact with X API v2 endpoints. | 3 / 3 |
Completeness | Clearly answers both what ('A CLI tool for making authenticated requests to the X (Twitter) API') and when ('Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'tweets', 'reply', 'quote', 'search', 'DMs', 'followers', 'X', 'Twitter', 'upload media', 'post'. Good coverage of common variations including both 'X' and 'Twitter'. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused on X/Twitter API interactions. The specific platform name and enumerated actions make it highly 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.
This is a solid, highly actionable skill reference for the xurl CLI with excellent security guardrails and comprehensive command coverage. Its main weaknesses are redundancy between the Quick Reference table and Command Details sections, and the lack of explicit validation/error-recovery steps in multi-step workflows. The content would benefit from being split across files given its length, keeping SKILL.md as a lean overview.
Suggestions
Eliminate redundancy by removing the Command Details section or merging unique details (like --media-id flags) into the Quick Reference table, moving verbose examples to a separate EXAMPLES.md file.
Add explicit validation checkpoints to workflows — e.g., after media upload, check the response for media_id before proceeding; after posting, verify the response contains a post ID.
Add a brief error recovery loop for rate limiting: e.g., 'If 429: wait 60s, retry. If 403: re-run xurl auth oauth2.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-organized but is quite long (~300+ lines) with some redundancy. The Command Details section largely repeats the Quick Reference table with minor additions. The Notes section contains some information Claude would already know (e.g., explaining what rate limits are). However, the security constraints and CLI syntax are genuinely useful new information. | 2 / 3 |
Actionability | Excellent actionability — every command is copy-paste ready with concrete examples, real flags, and specific syntax. The raw API access section, media upload workflow, and multi-app setup all provide fully executable commands with clear expected behavior. | 3 / 3 |
Workflow Clarity | Common Workflows section provides clear multi-step sequences (post with image, reply to conversation, search and engage), but lacks validation checkpoints. For example, the media upload workflow doesn't check if the upload succeeded before posting, and there's no guidance on handling the 429 rate limit errors beyond 'wait and retry'. The error handling section is informational rather than providing actionable recovery steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful Quick Reference table, but it's monolithic — everything is in one large file. The Command Details section could be split into a separate reference file, with SKILL.md serving as a concise overview pointing to detailed docs. No external file references are used despite the content length warranting it. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
0c1ec2b
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.