Twitter/X platform integration. Post tweets, read timeline, manage followers, and analyze engagement.
Install with Tessl CLI
npx tessl i github:Demerzels-lab/elsamultiskillagent --skill twitter67
Quality
52%
Does it follow best practices?
Impact
97%
1.14xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/twitter/SKILL.mdDiscovery
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 clear, concrete actions. However, it lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill. The platform-specific terminology provides good distinctiveness.
Suggestions
Add a 'Use when...' clause with trigger terms like 'when the user wants to post to Twitter, check their feed, or analyze social media engagement'
Include additional natural trigger terms users might say: 'social media', 'tweet something', 'X post', 'retweet', 'mentions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Post tweets, read timeline, manage followers, and analyze engagement' - these are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance to indicate when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes 'Twitter/X', 'tweets', 'timeline', 'followers', 'engagement' which are relevant keywords, but missing common variations like 'post', 'social media', 'retweet', 'mentions', '@' references. | 2 / 3 |
Distinctiveness Conflict Risk | Twitter/X is a specific platform with distinct terminology (tweets, timeline, followers). Unlikely to conflict with other social media skills due to platform-specific naming. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder or stub. While it's concise and well-structured, it provides no actionable guidance—just a feature list and natural language example prompts. Claude cannot execute any Twitter operations based on this content alone.
Suggestions
Add executable code examples for core operations (e.g., posting a tweet using the Twitter API with actual Python/curl code)
Include at least one complete workflow with steps, such as: authenticate -> compose tweet -> post -> verify success
Replace natural language 'Usage Examples' with actual API calls or SDK code snippets that Claude can execute
Add references to API documentation or separate files for advanced features like analytics and scheduling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient with no unnecessary explanations. It assumes Claude knows what Twitter is and how APIs work, listing only the essential setup and features. | 3 / 3 |
Actionability | The skill provides no executable code or concrete commands. The 'Usage Examples' are natural language prompts, not actual API calls or code snippets. There's no guidance on how to actually implement any of the listed features. | 1 / 3 |
Workflow Clarity | No workflows are defined. The skill lists features but provides no steps for accomplishing any task, no validation, and no sequence for multi-step operations like authentication flow or posting with media. | 1 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but it's essentially a stub with no references to detailed documentation. For a skill claiming multiple features (posting, analytics, scheduling), there should be links to detailed guides or examples. | 2 / 3 |
Total | 7 / 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.