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 a strong skill description that clearly identifies the tool's purpose, lists specific capabilities, and provides explicit trigger guidance with a 'Use this skill when...' clause. It uses third person voice appropriately and includes both the new brand name (X) and the legacy name (Twitter) for maximum discoverability. The description is concise yet comprehensive.
| 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 keywords 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 | Clearly scoped to X/Twitter API interactions with distinct triggers like 'tweets', 'DMs', 'followers', and 'X API v2'. Unlikely to conflict with other skills unless there are multiple Twitter-related 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. Its main weaknesses are verbosity (redundant quick reference + detailed sections, installation instructions, and explanatory notes that Claude doesn't need) and missing validation checkpoints in multi-step workflows like media upload. The content would benefit from splitting into a concise overview with references to detailed sub-files.
Suggestions
Remove the Quick Reference table or the Command Details section — having both is redundant. Keep the table as a quick lookup and move detailed examples to a separate REFERENCE.md.
Add validation steps to workflows: check `xurl media status --wait MEDIA_ID` before posting with media, and add error-checking guidance (e.g., verify non-zero exit codes between steps).
Move installation instructions, streaming details, and the Notes section to separate referenced files — the main skill should focus on usage patterns Claude needs.
Trim explanatory notes Claude already knows (rate limits concept, what token refresh means) to just the actionable parts (e.g., '429 → wait and retry; 403 → re-run `xurl auth oauth2`').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-organized but is quite long with some redundancy — the Quick Reference table duplicates much of the Command Details section, and the Notes section includes explanations Claude would already know (e.g., what rate limits are, how token refresh works). 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, specific flags, and real CLI syntax. The raw API access section and media upload workflow provide fully executable guidance. | 3 / 3 |
Workflow Clarity | Common Workflows section provides clear multi-step sequences, 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 rate limit errors (429) beyond 'wait and retry'. The post-with-media workflow should verify media processing status before attaching. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's monolithic — all content is inline in one large file. The detailed command examples, streaming docs, and auth setup could be split into separate reference files with links from the main skill. | 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
- trpc-group/trpc-agent-go
- Commit
af8bd5f
- 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.