Installable Skill
Turn TwtAPI into a Skill users can install right away
If your users do not want to start with API docs and request code, give them an installable Skill instead. The hosted gateway is already in place, so they only need to generate a skill_key and finish a short setup in OpenClaw or a compatible runner.
The setup is short
The public Skill handles the hosted entrypoint, so most users only need these three actions.
Generate a skill_key in the dashboard
Run clawhub install twtapi
Add TWTAPI_SKILL_KEY to env vars or a config file
Why Skill
Packaging the API as an installable entrypoint makes adoption easier
A Skill is a better fit for users who want to start using TwtAPI quickly without integrating the raw API first.
Lower onboarding friction
Users can start with installation and configuration instead of reading docs and wiring requests first.
Feels closer to a product
A Skill is easier to hand over as a ready-to-use capability than a bare API reference.
Separate auth boundary
A dedicated skill_key keeps Skill access isolated from your main API credentials.
Good for agent workflows
Compatible runners can call TwtAPI capabilities directly inside agentic or assisted workflows.
Best fit
When a Skill works better than a raw API
If the goal is fast adoption instead of custom integration, the Skill experience is usually much smoother.
Delivering to non-developers
When users only want the capability and do not want to build against an API themselves, the Skill path is easier.
Internal distribution
Teams can share one install command and one setup template across operators, analysts, and support staff.
Agent and automation stacks
When you need Twitter data capabilities inside a runner or automation system, the Skill model is a natural fit.
Quick start
Install the public Skill in 3 steps
We already host the gateway layer, so the user side only needs a key plus a short local setup.
1. Generate a Skill Key
Open the Skill tab in the dashboard and generate or rotate a `tsk-` prefixed skill_key.
2. Install the public Skill
Run `clawhub install twtapi` in a supported environment to install the public TwtAPI Skill.
3. Add config and restart
Set `TWTAPI_SKILL_KEY` in an environment variable or config file, then restart the runner.
Install templates
These three snippets are usually enough
You can hand these commands and templates to users as the default public Skill setup flow.
Install command
Install the public `twtapi` Skill package first.
After installation, add the generated skill_key and restart the client or runner.
clawhub install twtapi
Environment variable
The simplest option is to store the skill_key in an environment variable.
Replace `tsk-your-skill-key` with the real value from your dashboard.
export TWTAPI_SKILL_KEY="tsk-your-skill-key"
Config template
If the client uses a config file, you can write the Skill entry directly.
Save the updated template and restart the runner after replacing the example key.
{
"skills": {
"entries": {
"twtapi": {
"enabled": true,
"env": {
"TWTAPI_SKILL_KEY": "tsk-your-skill-key"
}
}
}
}
}FAQ
Common questions
Ship TwtAPI as an installable Skill for OpenClaw and compatible runners. The public Skill includes a hosted gateway, so users only need a dedicated skill_key.
How is Skill different from MCP?
MCP is for AI clients that speak the MCP protocol. Skill is a packaged, installable delivery format that fits skill runners and simpler distribution flows.
Do users need to host the gateway?
No. The public Skill already includes the hosted gateway, so users only need their own skill_key.
Why use a separate skill_key?
It keeps Skill access separate from your main API credentials, which makes rotation, access control, and troubleshooting much easier.
Give users an installable entrypoint before pushing them into a full API integration
If your goal is faster activation, a public Skill is often easier for users to adopt than raw API docs on day one.