CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 high-quality, execution-first skill body: every operation is backed by runnable code, and untrusted-content/security guidance is specific and well-reasoned rather than boilerplate. Remaining gaps are minor — duplicated search examples with a hardcoded personal username, and a missing retry loop in the posting workflow.

Suggestions

Replace the hardcoded personal username "affaanmustafa" with a placeholder (e.g., <username>) and merge the near-duplicate "Search Tweets" and "Pull Recent Original Posts" examples into one, varying only the query string.

Add a short retry/backoff loop to the posting workflow (reuse the rate-limit header read already shown) so the validate-and-recover path for the public write operation is explicit.

Consider moving the per-status error-handling matrix and media-upload details into a reference file so SKILL.md stays a leaner overview.

DimensionReasoningScore

Conciseness

The body is code-dominant and lean, with no tutorials on concepts Claude already knows, and the drift warning is justified time-sensitive framing. Not 5: "Pull Recent Original Posts for Voice Modeling" nearly duplicates the "Search Tweets" example, and examples hardcode a personal username ("from:affaanmustafa", "affaanmustafa") that should be a placeholder.

4 / 5

Actionability

Every operation ships copy-paste-ready executable code — real endpoints, env-var setup, response parsing, media upload, per-status error handling, and runtime rate-limit header reads. Not 4: the common cases (single tweet, thread, search, timeline, media post, failure modes) are all covered with complete runnable examples.

5 / 5

Workflow Clarity

"Integration with Content Engine" gives a numbered 7-step sequence with an explicit approval checkpoint ("Return the draft for approval… Post via X API only after approval"), and the error-handling section enumerates 201/429/403 paths. Not 5: the posting flow has no explicit validate-and-retry loop (e.g., re-checking on failure) — recovery guidance stops at raising exceptions.

4 / 5

Progressive Disclosure

No bundle files exist and none are referenced, so all references are real; sections are clearly headed (Auth, Core Operations, Rate Limits, Error Handling, Security) with the security sub-guidance well placed. Not 5: at ~235 lines, reference material such as the full error-handling matrix and media-upload details could be split into a separate file to keep SKILL.md a leaner overview.

4 / 5

Total

17

/

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: concrete, comprehensive, third-person, and clearly triggered, covering the X domain end-to-end. The only weakness is that the 'Use when' clause is generic rather than enumerating the natural trigger phrases users would actually say.

DimensionReasoningScore

Specificity

"posting tweets, threads, reading timelines, search, and analytics" plus "OAuth auth patterns, rate limits, and platform-native content posting" lists multiple concrete actions with comprehensive domain coverage in third-person voice. Not 4: there are no meaningful gaps in the action list.

5 / 5

Completeness

Both a clear what (posting, threads, reading timelines, search, analytics) and an explicit trigger clause "Use when the user wants to interact with X programmatically" are present. Not 5: the when clause is a single general statement rather than concrete trigger phrases naming user intents.

4 / 5

Trigger Term Quality

"X/Twitter API", "post tweets", "threads", "search", "analytics" give good natural keyword coverage including the X/Twitter synonym pair. Not 5: common user phrasings like "post to X", "send a tweet", or "read my mentions" appear only in the body, not the description.

4 / 5

Distinctiveness Conflict Risk

"X/Twitter API integration" carves out a clear niche with distinct platform-named triggers; minimal risk of firing for generic API or social-media skills. Not 4: nothing in the description overlaps with adjacent skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

skills/x-api/SKILL.md

Reviewed

Table of Contents

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.