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.
89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and has a clear distinctive niche around X/Twitter API interactions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media' - these are all distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('CLI tool for making authenticated requests to X API') and when ('Use this skill when you need to post tweets, reply, quote, search...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'tweets', 'reply', 'quote', 'search', 'DMs', 'followers', 'X', 'Twitter', 'media'. These match how users naturally describe Twitter/X interactions. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused on X/Twitter API specifically. The combination of platform name (X, Twitter) and specific actions (tweets, DMs, followers) makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%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, highly actionable skill with excellent concrete examples and clear workflows. The security guidance is appropriately thorough. Main weakness is length - the comprehensive command reference could be split into separate files for better progressive disclosure, and some content (Quick Reference vs Command Details) is redundant.
Suggestions
Consider moving the detailed 'Command Details' section to a separate COMMANDS.md file, keeping only the Quick Reference table in the main skill
Remove redundancy between Quick Reference table and Command Details - the table alone may suffice for most use cases with a link to detailed docs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally efficient but includes some redundancy - the Quick Reference table duplicates information from Command Details, and some explanations (like the Notes section) could be tightened. The security warnings are appropriately detailed given their importance. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready commands throughout. Every operation has concrete examples with real command syntax, and common workflows show complete multi-step processes with actual commands. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced (e.g., 'Post with an image' shows upload then post with explicit steps). The auth setup workflow includes validation via 'xurl auth status', and error handling section explains what to do when things fail. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (~300 lines) and could benefit from splitting detailed command references into separate files. The Quick Reference table helps navigation, but advanced topics like raw API access and streaming could be external references. | 2 / 3 |
Total | 10 / 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 | |
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.