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.
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
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 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 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', '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 highly actionable skill with excellent concrete examples and strong security guardrails for credential handling. Its main weaknesses are verbosity (the Command Details section largely duplicates the Quick Reference table) and lack of validation checkpoints in multi-step workflows. The content would benefit from being split across files given its length, with SKILL.md serving as a concise overview.
Suggestions
Remove or significantly condense the Command Details section since it largely duplicates the Quick Reference table — keep only examples that add genuinely new information (e.g., media upload workflow, raw API access).
Add validation/error-recovery steps to Common Workflows, e.g., check `xurl media status --wait MEDIA_ID` before posting with media, and handle 429 rate limit errors with retry guidance.
Split detailed command references and streaming/raw API sections into separate files (e.g., COMMANDS.md, RAW_API.md) and link from SKILL.md to keep the main file as a concise overview.
| 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 slightly more examples. The Notes section at the end contains information Claude would generally know (e.g., what rate limits are, what 429 means). However, the security constraints and CLI-specific syntax genuinely earn their place. | 2 / 3 |
Actionability | Excellent actionability throughout — every command is copy-paste ready with concrete examples, real flags, and realistic arguments. The media upload workflow, raw API access, 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 none include validation checkpoints or error recovery steps. For example, the media upload workflow doesn't check media status before posting, and there's no guidance on what to do if upload fails. The error handling section is separate and generic rather than integrated into workflows. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful Quick Reference table, but everything is in a single monolithic file. The Command Details section could be split into separate reference files, with SKILL.md serving as an overview pointing to them. 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 | |
- Repository
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.