twitter

Twitter/X platform integration. Post tweets, read timeline, manage followers, and analyze engagement.

1.14x

Quality

45%

Does it follow best practices?

Impact

97%

1.14x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/twitter/SKILL.md

Quality

Content

22%

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. It lists features and shows environment variable setup but provides zero actionable implementation details—no API endpoints, no library code, no concrete commands. Claude would be unable to perform any of the described tasks based on this content alone.

Suggestions

Add executable code examples for core operations (e.g., posting a tweet, reading timeline) using a specific library like tweepy, with complete, copy-paste-ready Python snippets.

Define a clear workflow for authentication and API interaction, including validation steps (e.g., verifying credentials before posting, checking rate limits).

Replace the vague feature bullet list with concrete API call patterns or tool invocations that Claude can directly execute.

Either add bundle files with detailed references for advanced features (analytics, scheduling) or inline the essential implementation details for at least the primary use cases.

Dimension	Reasoning	Score
Conciseness	Reasonably brief but the feature bullet list is vague filler that doesn't teach Claude anything actionable. The description line repeats the title. Some tokens are wasted on listing features without substance.	2 / 3
Actionability	No executable code, no API calls, no concrete commands or library usage. The 'Usage Examples' are natural language prompts, not actionable implementation guidance. Claude would not know how to actually post a tweet or read a timeline from this skill.	1 / 3
Workflow Clarity	There is no workflow, no sequencing of steps, and no validation. Setup shows environment variables but never explains how they're used. There's no indication of what tools, libraries, or APIs to call, let alone in what order.	1 / 3
Progressive Disclosure	The content is short and has some section structure (Setup, Features, Usage Examples), but there are no references to deeper documentation, no bundle files, and the features list promises capabilities with zero supporting detail or pointers to where that detail lives.	2 / 3
	Total	6 / 12 Passed

Description

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.

The description does a good job listing specific capabilities and clearly identifying its niche as Twitter/X integration. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding common user trigger phrases would also improve discoverability.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks to post on Twitter/X, check their feed, manage social media accounts, or analyze tweet performance.'

Include additional natural trigger terms users might say, such as 'social media', 'retweet', 'likes', 'DMs', 'thread', or 'post on X'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Post tweets, read timeline, manage followers, and analyze engagement.' These are distinct, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes 'Twitter/X', 'tweets', 'timeline', 'followers', and 'engagement' which are relevant keywords. However, it misses common user variations like 'post on X', 'social media', 'retweet', 'likes', or 'DMs'.	2 / 3
Distinctiveness Conflict Risk	The description is clearly scoped to Twitter/X specifically, with platform-specific terminology like 'tweets', 'timeline', and 'followers'. This is unlikely to conflict with other social media or general skills.	3 / 3
	Total	10 / 12 Passed

Validation

81%

Warnings & errors only

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: teeclaw/phorm-nft
Commit: 02adecb

Reviewed: 4 months ago

Table of Contents

Discovery Implementation Validation

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.