本文へ移動
cccskills
無料GitHub で公開

x-reply-drafter

Draft a reply or a value-add quote tweet for a specific X (Twitter) tweet from its URL. Use to reply in a thread, answer a creator, or quote-tweet with added value. Parses the tweet URL, reads pasted context, decides reply vs quote tweet, and drafts 1-3 variants in your voice. X has no LinkedIn-style 2-level thread flattening, so a reply is just a tweet. Publora has no reply endpoint, so the draft is returned as a copy-paste block to post yourself. Not for top-level posts (use x-post-writer).

インストール方法を見る

含まれるファイル(2)

  • SKILL.md6.4 KB
  • references/reply-templates.md2.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

X Reply Drafter

Drafts a reply in a thread, or a quote tweet, for a specific tweet. On X a reply is just a tweet posted in-reply-to another, and replies nest naturally: there is no LinkedIn-style 2-level flattening and no parent-comment URN to resolve.

When to use

  • User pastes a tweet URL and says "reply to this"
  • A creator replied to the user and they want to continue the thread
  • User wants to quote-tweet a take and add value (not a cheap dunk)

Input

An X tweet URL (x.com/HANDLE/status/ID or the twitter.com equivalent), plus the tweet text (and any thread context) pasted by the user, since this bundle has no built-in tweet reader.

Output

  • 1-3 reply or quote-tweet drafts, each under 280 chars
  • A reply vs quote tweet recommendation with the reason
  • A short context summary (who said what)
  • An approval card. On approval the draft is returned as a copy-paste block.

Reply vs quote tweet

Use a reply whenUse a quote tweet when
You are adding to the conversation in placeYour addition deserves its own reach
You are answering a question or engaging a creatorYour followers should see the original for context
You want intimacy over reachYou want reach and a take on your own timeline

Default to a reply for direct engagement and a quote tweet when the user's point is strong enough to stand as its own post. Never quote-dunk on a small account; add value or skip it.

Steps

Voice profile first (all drafts). If ../../references/voice-profile.md has filled: yes, load it and match the user's voice fingerprint, hard rules, and CTA/link style throughout. If it is not filled, mention once that x-humanizer --mode profile can learn their voice from a few posts, then proceed with the generic voice rules.

Story bank next. If ../../references/story-bank.md has filled: yes, load it and take every concrete detail (numbers, dates, named projects, positions) from there instead of asking mid-draft. Never invent a figure, a date or a client name that is not in the bank or supplied by the user in this conversation. If the bank has nothing that fits, ask the user, or say once that x-humanizer --mode interview fills it in 20 to 40 minutes. A draft with a plausible invented number is worse than a draft with none: one is vague, the other is a retraction.

  1. Parse the URL. lib.url_parser.parse_x_url(url) returns handle, tweet_id, canonical_url.
  2. Read the context. Ask the user to paste the target tweet and the relevant thread above it. If the user is already in the thread, include their prior tweet.
  3. Decide reply vs quote tweet using the table above. Recommend one, but let the user override.
  4. Draft 1-3 variants using references/reply-templates.md. If the counterpart asked a question, answer it plainly with one real detail. If they pushed back, concede then sharpen.
  5. Humanizer pass. Scrub 2026 AI vocab by density, cap em dashes (at most one per reply, never swap one for a period), strip reveal bridges and sincerity openers ("not gonna lie", "let me be honest"). Leave the rhythm alone; never insert a fragment for punch. Keep each variant under 280 chars (emoji = 2). One idea per reply. Canonical rules: x-humanizer V3.
  6. Approval card. Show the thread context, the variants, the reply-vs-quote recommendation, and the target URL.
  7. On approval. Call lib.publish(kind="reply", draft_text=<approved>, target_url=<canonical_url>) for a reply, or kind="quote" for a quote tweet. Publora has no reply endpoint, so kind="reply" always returns a copy-paste block. A kind="quote" could in principle post a new tweet containing the original URL via Publora, but the default is still copy-paste so the user controls the embed. Paste it on X yourself.

The no-flattening note

Unlike LinkedIn (which flattens reply threads to 2 levels and needs the top-level comment URN as the parent), X nests replies naturally. There is no parent-comment URN to compute. A reply is simply a tweet you post while replying to the target tweet. This skill therefore does not walk any comment tree; it just drafts the text and hands it back for you to post in-reply.

Templates (references/reply-templates.md)

  • R1 Answer-Their-Question - they asked, you answer plainly plus one real detail
  • R2 Concede-Then-Sharpen - "fair, and the part I would push on is Y"
  • R3 Extend-Their-Point - take their point one layer deeper with a new framing
  • R4 Share-Lived-Experience - "we hit this last quarter, here is what broke"
  • R5 Value-Add Quote - quote tweet that adds the missing nuance (X4 shape)

Hard rules

Global voice rules: see root SKILL.md Voice rules. Additional skill-specific rules:

  • Under 280 chars (emoji = 2). Replies are tighter than posts.
  • Never paste a canned "great point!". Respond with content or do not reply.
  • Do not hard-sell the user's product in a reply on someone else's tweet. Describe what they do instead.
  • Never quote-dunk on a small account. Add value or skip it.

Example

User: "Reply to this: https://x.com/somebuilder/status/1790000000000000000"

Skill: parses -> handle somebuilder, tweet 1790000000000000000. Asks the user to paste the tweet. User pastes a take about pricing. Skill recommends a reply (direct engagement), drafts an R2 Concede-Then-Sharpen variant and an R3 Extend-Their-Point variant, each under 280 chars. Shows the approval card.

User: "post the first one"

Skill: returns the copy-paste block with the target URL for the user to post as a reply on X.

Files

  • SKILL.md - this file
  • references/reply-templates.md - 5 reply/quote templates with examples

Related skills

  • x-post-writer - for a standalone tweet rather than a reply
  • x-thread-builder - for a multi-tweet response
  • x-humanizer - scrub the reply before posting

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Read your X (Twitter) audience and niche from real data. Pull a handle's recent tweets (yours or a competitor's) with likes, replies, and views, see which formats and hooks are working, read the repliers on a tweet (X gates likers, so repliers are the signal), and scan a niche query for top tweets. Powered by Apify, no login. Triggers on "analyze my tweets", "what is working on X", "read the replies", "competitor tweets", "who is engaging". Not for writing a tweet (use x-post-writer).

日本語の概要は準備中です。原文の説明を表示しています。

sergebulaev/x-skills1272026年10月7日 更新

Generate a weekly X (Twitter) content plan from a theme, audience, and content pillars. Produces per-day recommendations (single tweet vs thread, X hook formula, angle, posting time, primary goal), a single-to-thread mix, daily reply and quote-tweet targets, and a goal-mix balance check across replies, reposts, likes, and bookmarks. Use when the user wants to plan a week of X content instead of ad-hoc posting. Not for drafting one tweet (use x-post-writer) or one thread (use x-thread-builder).

日本語の概要は準備中です。原文の説明を表示しています。

sergebulaev/x-skills1272026年10月7日 更新

Reverse-engineer the hook from a viral X (Twitter) tweet or thread URL. Identifies which of the 10 canonical 2026 X formulas it uses (one-liner contrarian, data-point, build-in-public, quote-tweet, mini-list, relatable cold-open, listicle-thread, story thread, curiosity-gap, how-I teardown), explains why it worked, and returns a blank template mapped to your topic with its primary goal. Use to learn from a tweet you admire. Not for writing your own (use x-post-writer or x-thread-builder).

日本語の概要は準備中です。原文の説明を表示しています。

sergebulaev/x-skills1272026年10月7日 更新

Remove the AI tells human readers react to in a tweet or thread: 2026 vocabulary by density, reveal bridges, staccato stacks, stacked triads, performed sincerity. Also --mode audit (280-char fit and format), --mode profile (learns how you write) and --mode interview (fills your Story Bank: the numbers, turning points and positions posts are made of). Not for writing from scratch (use x-post-writer). Keywords: humanize, de-AI tweet, AI slop, interview me, audit before posting.

日本語の概要は準備中です。原文の説明を表示しています。

sergebulaev/x-skills1272026年10月7日 更新

Plan, draft, audit, and publish posts and threads for X (Twitter). Use when the user wants to write a single tweet or an auto-numbered thread, build a long-form tweetstorm, remove AI tells from a draft, reverse-engineer the hook from a viral tweet, draft a reply or quote tweet, or plan a week of X content. Tweets and threads publish via the Publora API, which auto-splits long content into a numbered thread. User provides notes or a tweet URL, the skill drafts, the user approves, then it publishes.

日本語の概要は準備中です。原文の説明を表示しています。

sergebulaev/x-skills1272026年10月7日 更新

Draft a single tweet or short auto-thread for X (Twitter) using a 2026 X hook formula (one-liner contrarian, data-point, build-in-public, mini-list, relatable cold-open), picked by goal (replies, reposts, likes, bookmarks). Respects the 280-char limit (25,000 on Premium), runs the humanizer pass, and publishes via Publora on approval. Use to write a tweet from notes. Not for long threads (use x-thread-builder) or auditing a draft (use x-humanizer --mode audit).

日本語の概要は準備中です。原文の説明を表示しています。

sergebulaev/x-skills1272026年10月7日 更新

sergebulaev のスキルをすべて見る

このスキルの問題を報告する