Read and post to X/Twitter via API. Check mentions, post tweets, search. Uses OAuth 2.0 user context with token refresh.
81
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
67%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 description effectively communicates specific capabilities for Twitter/X integration with good technical detail. However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know when to select it, and could benefit from additional natural trigger terms users might say when requesting Twitter functionality.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user wants to interact with Twitter/X, post updates, check their timeline, or search tweets'
Include additional natural trigger terms users might say: 'timeline', 'retweet', 'followers', 'social media post', '@mention'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Read and post to X/Twitter', 'Check mentions', 'post tweets', 'search', and specifies technical implementation 'OAuth 2.0 user context with token refresh'. | 3 / 3 |
Completeness | Clearly answers 'what' (read/post to Twitter, check mentions, search) but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes good keywords like 'X/Twitter', 'mentions', 'tweets', 'search', but missing common variations users might say like 'timeline', 'retweet', 'DM', 'followers', or the hashtag symbol. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche targeting X/Twitter specifically with platform-specific terms like 'tweets', 'mentions', and 'OAuth 2.0 user context' - unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%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, practical skill that provides exactly what Claude needs to interact with the X/Twitter API. The authentication setup and API examples are complete and executable. The main weakness is the lack of error handling guidance and validation steps for API operations, particularly for destructive actions like posting or deleting tweets.
Suggestions
Add error handling examples showing how to check response status codes and handle common failures (rate limits, auth errors)
Include a validation step before posting tweets (e.g., confirm tweet length, check for prohibited content patterns)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information. No explanation of what Twitter/X is or how OAuth works conceptually—just the practical details Claude needs. | 3 / 3 |
Actionability | Fully executable code examples with copy-paste ready Python snippets. Includes complete authentication setup, all common API calls with exact endpoints and parameters, and clear secret management commands. | 3 / 3 |
Workflow Clarity | Steps are clear (get secrets, create session, make calls, revoke leases), but lacks explicit validation checkpoints. No error handling guidance or feedback loops for failed API calls, which matters for operations like posting tweets. | 2 / 3 |
Progressive Disclosure | Well-organized single file appropriate for this scope. Clear sections (Authentication, Account Info, Common Operations, Rate Limits, Rules) with logical flow. No need for external references given the focused scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 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.