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

85%

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-first skill with a clear approval-gated workflow for the destructive posting step. Its main weakness is structure: it is a long monolithic document with no progressive disclosure into reference files.

Suggestions

Move exhaustive operation examples (e.g., media upload, voice-modeling pull) into a references/ file and link from SKILL.md so the main file stays an overview.

Add an explicit retry/backoff feedback loop in the error-handling section rather than only raising an exception on 429.

Trim minor explanatory prose like "Best for: read-heavy operations, search, public data" to keep the already-lean sections tighter.

Dimension	Reasoning	Score
Conciseness	Mostly lean code-first sections that assume Claude's competence, with only minor explanatory prose ("Best for: read-heavy operations", the rate-limit preamble) that could be trimmed, fitting the 4 anchor rather than a fully lean 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready Python covering the common cases — posting tweets/threads, search, timeline reads, media upload, and error handling — matching the 5 anchor.	5 / 5
Workflow Clarity	The Content Engine integration is a clear 7-step sequence with an explicit approval checkpoint before the destructive post step, and error handling covers 429/403; minor gaps (no explicit retry feedback loop) keep it at 4 rather than 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections but monolithic — all ~225 lines of API reference are inline with no bundle files and no one-level-deep references to separate materials, matching the 3 anchor where content that could be separate is inline.	3 / 5
	Total	16 / 20 Passed

Description

91%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, specific description that names concrete capabilities and includes an explicit activation clause with natural trigger terms. The only weakness is the "when" guidance being a single general phrase rather than enumerating concrete trigger situations.

Suggestions

Expand the "Use when..." clause to list concrete trigger phrases (e.g., "Use when the user asks to post a tweet or thread, read a timeline, search X, or track engagement").

Add a few more natural trigger synonyms users might say (e.g., "post to X", "tweet this") to the description itself, not just the body.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "posting tweets, threads, reading timelines, search, and analytics" plus "OAuth auth patterns, rate limits, and platform-native content posting" — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Clearly states the "what" and includes an explicit "Use when the user wants to interact with X programmatically" trigger, but the "when" is a single general phrase rather than multiple concrete trigger conditions, fitting the 4 anchor better than 5.	4 / 5
Trigger Term Quality	Includes natural terms users actually say ("post tweets", "threads", "search", "X", "Twitter") with synonyms for the platform, matching the comprehensive-synonyms anchor.	5 / 5
Distinctiveness Conflict Risk	Scopes tightly to X/Twitter API integration with distinct triggers, and the platform-specific framing keeps conflict risk with adjacent content skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

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

Reviewed: 1 day 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.