How do I install the Neomano X skill?

Run npx skillmds@latest add lord1egypt/neomano-x in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Neomano X safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Neomano X?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Neomano X free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Neomano X?

Lord1Egypt (@lord1egypt) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Neomano X by lord1egypt — Agent Skill

Name: Neomano X
Rating: 4.666666666666667 (3 reviews)
Author: Lord1Egypt

Neomano X

Draft, revise, and publish X (Twitter) posts with an image using the X API. Use when the user asks for a tweet/post for X, wants to attach an image, and requires a human approval step (“PUBLICAR” or “PUBLISH”) before actually posting.

Lord1Egypt Updated Sep 8, 2026 2 repo stars

File contents

Safety / approval rule (mandatory)

Never publish unless the user explicitly replies with PUBLICAR or PUBLISH (uppercase).
Before publishing, always show the final text + the image you will use.

Credentials (do not hardcode)

Provide these as environment variables (recommended: ~/.openclaw/.env on the gateway machine):

X_API_KEY
X_API_SECRET
X_ACCESS_TOKEN
X_ACCESS_TOKEN_SECRET

One-time setup

1) Create the venv (once)

python3 {baseDir}/scripts/bootstrap_venv.py

Rationale: this avoids system-wide installs (PEP 668 / externally-managed Python) and keeps dependencies isolated to this skill.

Note: the .venv/ directory is intentionally not shipped in the skill package; each user creates it locally.

2) If you do NOT have Access Token Secret (UI changed)

Use the OAuth 1.0a 3‑legged flow to obtain X_ACCESS_TOKEN + X_ACCESS_TOKEN_SECRET.

Prereq: set an allowed callback URL in your X app settings (any HTTPS URL is fine, even a dummy page). Recommended: set X_OAUTH_CALLBACK=https://example.com/callback (and whitelist it in the app).

Start:

# run inside the venv
python3 {baseDir}/scripts/run.py dry-run --text "(noop)"  # just to verify venv exists
{baseDir}/.venv/bin/python {baseDir}/scripts/oauth1_flow.py auth-start

Open the printed AUTH_URL, approve, then copy oauth_verifier from the browser redirect URL.

Finish:

{baseDir}/.venv/bin/python {baseDir}/scripts/oauth1_flow.py auth-finish \
  --oauth-token "..." \
  --oauth-token-secret "..." \
  --oauth-verifier "..."

Workflow

Ask for: tweet text idea + the image (a local path or an inbound media file path).
Produce a draft tweet (and alt-text suggestion for the image).
Iterate revisions until the user is happy.
When the user says PUBLICAR or PUBLISH:

python3 {baseDir}/scripts/run.py publish --text "..." --image "/path/to/image.jpg"

If the user did not approve, only run dry-run:

python3 {baseDir}/scripts/run.py dry-run --text "..." --image "/path/to/image.jpg"

Notes

Image upload uses the v1.1 media upload endpoint.
Tweet creation uses the v2 tweets endpoint.

---name: neomano-xdescription: Draft, revise, and publish X (Twitter) posts with an image using the X API. Use when the user asks for a tweet/post for X, wants to attach an image, and requires a human approval step (“PUBLICAR” or “PUBLISH”) before actually posting.---## Safety / approval rule (mandatory)- Never publish unless the user explicitly replies with **PUBLICAR** or **PUBLISH** (uppercase).- Before publishing, always show the final text + the image you will use.## Credentials (do not hardcode)Provide these as environment variables (recommended: `~/.openclaw/.env` on the gateway machine):- `X_API_KEY`- `X_API_SECRET`- `X_ACCESS_TOKEN`- `X_ACCESS_TOKEN_SECRET`## One-time setup### 1) Create the venv (once)```bashpython3 {baseDir}/scripts/bootstrap_venv.py```Rationale: this avoids system-wide installs (PEP 668 / externally-managed Python) and keeps dependencies isolated to this skill.Note: the `.venv/` directory is intentionally *not* shipped in the skill package; each user creates it locally.### 2) If you do NOT have Access Token Secret (UI changed)Use the OAuth 1.0a 3‑legged flow to obtain `X_ACCESS_TOKEN` + `X_ACCESS_TOKEN_SECRET`.Prereq: set an allowed callback URL in your X app settings (any HTTPS URL is fine, even a dummy page).Recommended: set `X_OAUTH_CALLBACK=https://example.com/callback` (and whitelist it in the app).Start:```bash# run inside the venvpython3 {baseDir}/scripts/run.py dry-run --text "(noop)" # just to verify venv exists{baseDir}/.venv/bin/python {baseDir}/scripts/oauth1_flow.py auth-start```Open the printed `AUTH_URL`, approve, then copy `oauth_verifier` from the browser redirect URL.Finish:```bash{baseDir}/.venv/bin/python {baseDir}/scripts/oauth1_flow.py auth-finish \ --oauth-token "..." \ --oauth-token-secret "..." \ --oauth-verifier "..."```## Workflow1. Ask for: tweet text idea + the image (a local path or an inbound media file path).2. Produce a **draft** tweet (and alt-text suggestion for the image).3. Iterate revisions until the user is happy.4. When the user says **PUBLICAR** or **PUBLISH**:```bashpython3 {baseDir}/scripts/run.py publish --text "..." --image "/path/to/image.jpg"```If the user did not approve, only run dry-run:```bashpython3 {baseDir}/scripts/run.py dry-run --text "..." --image "/path/to/image.jpg"```## Notes- Image upload uses the v1.1 media upload endpoint.- Tweet creation uses the v2 tweets endpoint.

Frequently asked questions