x-api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, code-complete skill body that assumes Claude's competence and avoids teaching basics. Its weaknesses are a monolithic inline structure with no progressive disclosure and a missing retry loop for the batch thread flow.

Suggestions

Extract the per-operation API snippets into a reference file (e.g. references/operations.md) and keep SKILL.md as an overview with one-level-deep links, improving progressive disclosure.

Add an explicit validate->retry loop to the thread-posting example (handle 429/429 mid-thread, resume from last posted id) to satisfy the batch-operation feedback-loop expectation.

Deduplicate the two near-identical recent-search code blocks into one parameterized example to trim tokens.

Dimension	Reasoning	Score
Conciseness	The body is largely lean code-forward guidance with no padding about what X is or how libraries work, but the duplicate search snippets (two near-identical recent-search blocks, one labeled 'voice modeling') and the non-executable prose around rate limits could be trimmed slightly.	4 / 5
Actionability	Copy-paste ready executable Python for every core operation (post, thread, timeline, search, media upload), with explicit env-var setup and OAuth wiring; the common cases are fully covered.	5 / 5
Workflow Clarity	The content-engine integration section gives a clear 7-step sequence with an explicit 'return draft for approval' checkpoint, and error handling covers 201/429/403, but there is no explicit validate->fix->retry loop for the batch thread-posting flow, which the rubric flags as a feedback-loop gap.	4 / 5
Progressive Disclosure	No bundle files exist and the SKILL.md inlines the full API reference (every operation with code), so content that could be split into a reference file is monolithic; section headers are present but no one-level-deep references are signaled.	3 / 5
	Total	16 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states capabilities and provides an explicit trigger clause, using third person throughout. Minor gaps in trigger synonyms and secondary capability coverage keep it just below perfect.

Suggestions

Add natural user phrasings like 'post to Twitter' or 'send a tweet' alongside the existing X-centric triggers to broaden trigger coverage.

Mention media upload and DMs if they are supported, since 'analytics' and 'threads' are listed but these are absent.

Keep the X/Twitter dual naming but clarify the platform (e.g. 'X (formerly Twitter)') to reduce overlap ambiguity with cross-posting skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('posting tweets, threads, reading timelines, search, and analytics') plus secondary concerns (OAuth patterns, rate limits), with only minor coverage gaps such as media upload and DMs.	4 / 5
Completeness	Explicitly answers both 'what' (posting, reading, search, analytics, OAuth, rate limits) and 'when' ('Use when the user wants to interact with X programmatically') with a concrete trigger clause.	5 / 5
Trigger Term Quality	Strong natural terms ('X', 'Twitter', 'tweet', 'X API', 'Twitter API', 'threads') but misses common user phrases like 'post to Twitter' and lacks synonym variations beyond X/Twitter.	4 / 5
Distinctiveness Conflict Risk	Clear X/Twitter niche with distinct triggers, but the platform migration (Twitter→X) and overlap with generic 'crosspost'/'content-engine' skills introduces minor conflict risk.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/x-api/SKILL.md
Commit: 8321021

Reviewed: 6 days 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.