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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

Highly actionable, executable content with a well-sequenced, approval-gated integration workflow and solid error-handling feedback loops. It loses points on conciseness (redundant search examples and restated trigger lists) and on progressive disclosure (everything lives in one monolithic file with no external references).

Suggestions

Collapse the two near-identical 'Search Tweets' and 'Pull Recent Original Posts for Voice Modeling' sections into one parameterized search example, or move the voice-modeling variant into the content-engine integration context where it's used.

Trim the 'When to Activate' bullet list or the intro line so the body doesn't restate the frontmatter description verbatim.

Consider extracting the full Core Operations API catalog into a references/REFERENCE.md (one level deep) so SKILL.md stays a lean overview with a clear quick-start example.

Dimension	Reasoning	Score
Conciseness	The code is lean and assumes Claude's competence (no OAuth/PDF-style concept padding), but there is real redundancy: two near-identical search/recent examples ('Search Tweets' and 'Pull Recent Original Posts for Voice Modeling') and an intro plus 'When to Activate' list that restate the frontmatter description — content that could be tightened.	2 / 3
Actionability	Every operation ships as fully executable Python with real endpoints (https://api.x.com/2/tweets), real env vars, real query syntax (from:affaanmustafa -is:retweet), and raise_for_status() — copy-paste ready, not pseudocode.	3 / 3
Workflow Clarity	The 'Integration with Content Engine' section is a clear numbered sequence with an explicit approval checkpoint (steps 5–6: 'Return the draft for approval ... Post via X API only after approval'), and the Error Handling section provides feedback loops for 429/403 recovery, satisfying the validation-checkpoint anchor for this outward-facing action.	3 / 3
Progressive Disclosure	The file is a single ~225-line monolithic SKILL.md with no references/, scripts/, or assets/ bundle files; it is well-sectioned by headers but the per-operation API catalog is content that arguably should be split into a one-level-deep reference, and no progressive-disclosure references are signaled — fitting the 'structured but inline' anchor rather than the split/3 anchor or the disorganized/1 anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%

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, concise description that names concrete capabilities, includes explicit 'Use when' trigger guidance, and occupies a clear platform niche. It avoids vague fluff and third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'posting tweets, threads, reading timelines, search, and analytics' plus 'OAuth auth patterns, rate limits, and platform-native content posting' — matching the multi-action anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	It explicitly answers both 'what' (the integration capabilities listed) and 'when' via the 'Use when the user wants to interact with X programmatically' trigger, satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	It surfaces natural terms users actually say ('tweet', 'threads', 'X/Twitter API', 'timeline', 'search') and an explicit 'Use when the user wants to interact with X programmatically' clause, giving good coverage rather than just jargon.	3 / 3
Distinctiveness Conflict Risk	The X/Twitter platform niche with distinct triggers ('X/Twitter API', 'tweet') makes it unlikely to fire for unrelated skills, matching the clear-niche anchor; related skills like crosspost/content-engine cover different concerns.	3 / 3
	Total	12 / 12 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
Commit: 4130457

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.