x-api
by affaan-mx-api helps you work with the X/Twitter API for posting, reading timelines, search, and basic analytics. It guides auth choices, endpoint selection, and request shape for API Development tasks, including bearer-token reads and OAuth 1.0a write flows.
This skill scores 78/100, which means it is a solid listing candidate for directory users who need X/Twitter API guidance. It clearly supports common triggers like posting, searching, reading timelines, and handling auth patterns, so users can judge fit quickly, though the install decision is tempered by the lack of a dedicated install command and supporting reference files.
- Clear activation cues for posting, reading, searching, and analytics workflows on X
- Concrete auth examples for both app-only bearer tokens and user-context OAuth 1.0a
- Substantive SKILL.md content with structured headings and code examples that reduce guesswork
- No install command or companion scripts/references, so adoption may require manual setup
- Coverage appears centered on core API usage; users needing deeper operational edge cases may need external docs
Overview of x-api skill
What x-api does
The x-api skill helps you work with the X/Twitter API for programmatic posting, reading, search, and basic analytics. It is most useful when you need an x-api skill that turns a vague request like “post this update” or “pull recent mentions” into the right auth model, endpoint choice, and request shape.
Who should install it
Install x-api if you build bots, social automation, content publishing pipelines, or internal tools that need X data. It is especially relevant for API Development tasks where you need to decide whether the job is read-only, user-context write access, or search-heavy.
What makes it useful
The main value of x-api is practical routing: it distinguishes bearer-token use for app-only reads from OAuth 1.0a for posting and account actions. That reduces guesswork around permissions, rate limits, and which inputs the API actually needs before you start coding.
How to Use x-api skill
Install and load the skill
Use the directory’s install flow for x-api and then read SKILL.md first. If your environment supports it, install with:
npx skills add affaan-m/everything-claude-code --skill x-api
Then inspect any linked repository context the skill provides. In this repo, the main source file is skills/x-api/SKILL.md, and there are no companion rules/, resources/, or helper scripts to fill in missing behavior.
Give the skill the right task shape
The x-api usage works best when you specify three things up front: the action, the access level, and the target object. For example, say “search recent posts about Claude Code with a bearer token” or “post a thread from user context with OAuth 1.0a.” That is much better than “help me use X API,” because the skill can map your intent to the correct authentication and endpoint path.
Use the right input details
For read flows, include the search query, date window, result limits, and whether you need public data or account-specific data. For write flows, include the exact post text, whether threading is required, and any media or reply constraints. If you are building x-api for API Development, also state your runtime, secret storage method, and whether you need sample code in Python, JavaScript, or shell.
Read the source in this order
Start with SKILL.md, then review the authentication section and the “When to Activate” guidance. Those parts tell you whether the request belongs in this skill at all. If you are adapting it into your own workflow, copy the decision logic first, not the code sample, because auth choice is the main adoption blocker for most x-api install attempts.
x-api skill FAQ
Is x-api only for posting tweets?
No. The x-api skill covers posting, reading timelines, searching recent content, and analytics-oriented retrieval. If your job is only to draft copy, a general writing prompt is enough; if you need the content to reach X through the API, x-api is the better fit.
Do I need to know OAuth before using it?
You do not need to be an OAuth expert, but you do need to know whether your task is app-only read access or user-context write access. That is the main boundary in this x-api guide, and it determines which credentials you must provide before any request can work.
When should I not use this skill?
Do not use x-api if you only need a one-off manual social post, if your org has not approved X API access, or if you cannot supply secure environment variables. It is also a poor fit when your requirement is broader social listening across platforms, because the skill is X-specific.
How to Improve x-api skill
Specify the outcome, not just the endpoint
Better inputs produce better x-api outputs. Instead of asking for “an API call,” ask for “a Python example that searches recent posts for claude code, returns 10 results, and uses a bearer token from env vars.” Concrete success criteria help the skill avoid generic or incomplete examples.
Provide auth and permission constraints
Most failures come from missing access details. Tell the skill whether you have bearer-token access, OAuth 1.0a user context, or both, and mention any constraints like no stored secrets, no DMs, or read-only access. That prevents the skill from recommending an auth flow you cannot actually use.
Iterate from the first working request
Start with one endpoint and one narrow use case, then expand. A strong x-api workflow is: verify authentication, run a small read request, confirm rate-limit behavior, then add posting or analytics. If the first output is too abstract, ask for the exact request, expected response shape, and minimal error handling rather than a broader rewrite.