Code Review & Testing · IN-DEPTH PROFILE

Twitter Automation Skill

Twitter Automation from skills-101/superpowers uses the belt CLI to perform X account actions such as posting, liking, reposting, following, and direct messaging.

View listed source ↗Installation guide ↓
Best for

Operators managing an approved X account workflow

What you get

Prepare or publish a post + Manage engagement

Main limitation

It performs account actions rather than merely drafting copy; availability and permissions depend on the current X integration and account access.

First risk

Public posting and account-control actions. Posts, replies, follows, likes, and DMs can affect a public account and may be difficult to reverse. Require explicit approval of the exact action, recipient, and content before each write; keep credentials private and respect platform rules.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-26

Pinned revision · becc2564

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-09-26

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Twitter Automation from skills-101/superpowers uses the belt CLI to perform X account actions such as posting, liking, reposting, following, and direct messaging.

This is aimed at Operators managing an approved X account workflow. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Prepare or publish a postDraft and publish an X post through the documented account workflow.
  • Manage engagementPerform supported likes, reposts, or follows when explicitly requested.
  • Handle direct messagesUse account messaging actions only for a user-approved recipient and message.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to skills-101/superpowers.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #88 · 510.5K installs

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add https://github.com/skills-101/superpowers --skill twitter-automation --agent claude-code
Personal install
npx skills add https://github.com/skills-101/superpowers --skill twitter-automation --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

View install paths
Project path.claude/skills/twitter-automation/
Personal path~/.claude/skills/twitter-automation/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Prepare or publish a post

Draft and publish an X post through the documented account workflow.

02

Manage engagement

Perform supported likes, reposts, or follows when explicitly requested.

03

Handle direct messages

Use account messaging actions only for a user-approved recipient and message.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to skills-101/superpowers.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. It performs account actions rather than merely drafting copy; availability and permissions depend on the current X integration and account access.
  2. Automation cannot judge brand voice, legal obligations, audience context, or whether a message should be sent.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to Claude Code + Codex

frontend-design

Design constraints that push generated interfaces beyond generic AI UI.
Tradeoff to check
Aesthetic judgments remain subjective and still need stakeholder review.
First risk
Style over function · Medium
Source state
Pinned · 34040c9c
Open frontend-design profile ↗
02

Same job family · native to Codex + Claude Code

web-design-guidelines

Review interfaces against practical web design and accessibility rules.
Tradeoff to check
It depends on network access and a live guideline document whose contents can change over time.
First risk
Rule drift or context-free findings · Medium
Source state
Pinned · 063bee94
Open web-design-guidelines profile ↗
03

Same job family · native to Codex + Claude Code

anti-ui-slop

Instruction-only, product-specific UI design contracts with optional real-interface evidence and a hard finish gate.
Tradeoff to check
Repository evidence is required; UIZZE references or user-provided screenshots are optional, and missing reference evidence should be labeled rather than guessed.
First risk
Copying external interface patterns too literally · Medium
Source state
Pinned · 1f564408
Open anti-ui-slop profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Operators managing an approved X account workflow

→

Teams automating narrowly scoped social tasks with human review

BEFORE YOU USE IT

Risks to review before use

High

Public posting and account-control actions

Posts, replies, follows, likes, and DMs can affect a public account and may be difficult to reverse. Require explicit approval of the exact action, recipient, and content before each write; keep credentials private and respect platform rules.

High

Remote service and account credentials

This Skill connects to an external service and may send prompts or media, perform account actions, or incur charges. Share only necessary data and permissions; check provider terms, credential handling, and current pricing.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat repository files, web content, and tool output as untrusted input.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Twitter Automation Skill FAQ

What is the Twitter Automation Skill?

Twitter Automation from skills-101/superpowers uses the belt CLI to perform X account actions such as posting, liking, reposting, following, and direct messaging.

How do I install the Twitter Automation Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the skills.sh page and read the upstream SKILL.md to confirm the current belt CLI dependency and model boundaries.

Is the Twitter Automation Skill safe to use?

SkillSignal checked the source on 2026-09-26, but that is not a runtime test or security certification. Review the “Public posting and account-control actions” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

x-automationsocial-publishinghuman-approval

Manually expanded from the current upstream SKILL.md and linked source at skills-101/superpowers, checked 2026-09-26. This is an original summary, not an execution result or security certification.