xurl
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 an excellent skill description that clearly identifies the tool's purpose, lists comprehensive concrete actions, and includes an explicit 'Use when' clause with natural trigger terms. It covers both the old (Twitter) and new (X) platform names, ensuring broad discoverability. The description is concise yet thorough, making it easy for Claude to select this skill 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', and 'X API v2'. Covers both the old name (Twitter) and new name (X). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around X/Twitter API interactions. The specific platform name and API version (v2) 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.
This is a highly actionable skill with excellent concrete examples and comprehensive CLI coverage, but it suffers from redundancy (Quick Reference duplicating Command Details) and verbosity that inflates the token cost. The workflow sections lack validation checkpoints for multi-step operations like media upload, and the entire document could benefit from splitting detailed reference content into separate files while keeping the SKILL.md as a concise overview.
Suggestions
Remove the Command Details section or the Quick Reference table to eliminate redundancy — keep the table as a quick lookup and move detailed examples to a separate REFERENCE.md file.
Add validation checkpoints to multi-step workflows, e.g., after media upload, check the response for media_id before proceeding; after posting, verify the response contains the new post ID.
Move installation instructions to a separate INSTALL.md — Claude doesn't need 20+ lines of installation options in every context window load.
Trim the Notes section by removing information already covered elsewhere (token storage warning is in Prerequisites, multiple apps is in Common Workflows).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-organized but contains significant redundancy — the Quick Reference table duplicates nearly all the Command Details section, and the Notes section repeats safety warnings already covered in Prerequisites. Some sections like Output Format explain things Claude already knows (JSON structure). The installation section is also lengthy for a skill file. | 2 / 3 |
Actionability | Excellent actionability throughout — 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 parameters. | 3 / 3 |
Workflow Clarity | Common Workflows section provides clear multi-step sequences (e.g., upload then post), but lacks validation checkpoints — there's no guidance on checking if media upload succeeded before posting, no error recovery loops for rate limits (just 'wait and retry'), and the media upload workflow doesn't verify the media_id was returned successfully before proceeding. | 2 / 3 |
Progressive Disclosure | The content is a single monolithic file at ~300+ lines that could benefit from splitting — the full Command Details section and installation instructions could be separate reference files. The Quick Reference table provides good overview structure, but the detailed sections that follow make the file very long without any references to external files for deeper content. | 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 | |
- Repository
- Hung-Reo/hungreo-openclaw
- Commit
e893157
- 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.