Pp X Twitter
Drive the Printing Press x-twitter-pp-cli from your agent to search, archive, monitor, and post on X without browser tab sprawl.
Overview
pp-x-twitter is an agent skill for the Launch phase that drives the x-twitter-pp-cli to search, archive, monitor, and post on X from your coding agent.
Install
npx skills add https://github.com/mvanhorn/printing-press-library --skill pp-x-twitterWhat is this skill?
- Agent skill for x-twitter-pp-cli: search, archive tweets, thread retrieval, mention monitoring, thread posting
- Install path via npx @mvanhorn/printing-press-library install x-twitter --cli-only with documented default bin locations
- Requires verifying CLI presence before any command—skill documents install-first flow
- Trigger phrases include search X for, post a thread to X, monitor my X mentions, use x-twitter
- Apache-2.0 Printing Press library mirror; edit library source not generated SKILL stub
- Go-based x-twitter-pp-cli binary
- Install via npx @mvanhorn/printing-press-library
Adoption & trust: 1 installs on skills.sh; 1.5k GitHub stars; 1/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You need repeatable X research and posting from agent workflows but keep losing time reinstalling CLIs and juggling browser-only tools.
Who is it for?
Indie founders and builders who launch on X and want agent-invokable CLI commands with an documented install path.
Skip if: Builders who do not use X, need fully managed SaaS schedulers only, or cannot install local Go CLIs on their machine.
When should I use this skill?
search X for, archive tweets about, show me the X thread for, monitor my X mentions, post a thread to X, use x-twitter, run x-twitter-pp-cli.
What do I get? / Deliverables
Your agent runs verified x-twitter-pp-cli commands for search, archives, mention monitoring, and thread posts inside one terminal-first flow.
- CLI command output
- Archived tweet collections
- Published X threads or posts
Recommended Skills
Journey fit
Launch distribution is where founders publish threads, watch mentions, and harvest social proof on X. The CLI backs outbound posts, mention monitoring, and research threads that feed launch and early traction plays.
How it compares
Printing Press CLI integration skill—not the X web app and not a standalone MCP server package.
Common Questions / FAQ
Who is pp-x-twitter for?
Solo builders using Claude-class agents who distribute on X and want Bash-driven search, archive, monitor, and post commands via x-twitter-pp-cli.
When should I use pp-x-twitter?
During Launch distribution for threads and mentions, and Grow content when archiving competitor or audience conversations for repurposing.
Is pp-x-twitter safe to install?
It runs a third-party CLI with network and API access; review the Security Audits panel on this Prism page, verify Apache-2.0 license, and scope API tokens minimally.
SKILL.md
READMESKILL.md - Pp X Twitter
<!-- GENERATED FILE — DO NOT EDIT. This file is a verbatim mirror of library/social-and-messaging/x-twitter/SKILL.md, regenerated post-merge by tools/generate-skills/. Hand-edits here are silently overwritten on the next regen. Edit the library/ source instead. See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". --> # X (Twitter) — Printing Press CLI ## Prerequisites: Install the CLI This skill drives the `x-twitter-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows: ```bash npx -y @mvanhorn/printing-press-library install x-twitter --cli-only ``` 2. Verify: `x-twitter-pp-cli --version` 3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill. If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.4 or newer). This installs into `$GOPATH/bin` (default `$HOME/go/bin`), so add that directory to `$PATH` instead: ```bash go install github.com/mvanhorn/printing-press-library/library/social-and-messaging/x-twitter/cmd/x-twitter-pp-cli@latest ``` If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds. Mirrors the official X v2 API and adds what no other X tool has: a local SQLite store you can sync once and query many times with FTS5 search and group-by analytics, agent-native --json/--select output, and an MCP server that exposes the whole surface to AI agents through token-efficient orchestration plus named multi-step intents. Reconstruct conversation threads offline with `thread show`, compose self-reply threads from markdown with `thread compose`, author long-form X Articles from markdown with `articles-publish-md`, and rescue your bookmark graveyard with `users bookmarks find` — keyword and author search over your synced bookmarks, which X itself gives you no way to search. ## When to Use This CLI Reach for this CLI when a task involves reading, searching, or archiving X (Twitter) data and you want the results queryable offline rather than re-fetched each time — building a searchable corpus of posts, reconstructing a conversation thread, snapshotting a user's recent posts with engagement, or monitoring mentions incrementally. It is also the right choice when an AI agent needs an X surface with read-only/destructive safety hints and named multi-step intents rather than a pile of raw endpoint calls. Prefer it over raw API calls whenever the same data will be queried more than once, since the local store avoids re-spending per-read credits. ## Unique Capabilities These capabilities aren't available in any other tool for this API. ### Local state that compounds - **`thread show`** — Rebuild a full conversation thread from your locally synced posts — ordered and depth-tagged — without re-spending API read credits. _When an agent needs the shape of a discussion (who replied to whom, in order), reach for this instead of paginating the search API and re-assembling the tree by han