AgentSkillsCN

x-post-creator

为SaaS产品创作高质量的X平台帖子,包括上线宣传、功能发布、客户案例分享、增长动态更新、创始人故事,以及以转化为核心的CTA号召。当您需要为SaaS语境下的X/Twitter撰写、改写、优化,或重新调整社交媒体帖子时,此功能将为您提供有力支持。

SKILL.md
--- frontmatter
name: x-post-creator
description: Create high-performing X posts for SaaS products, including launch posts, feature announcements, customer proof posts, growth updates, founder narratives, and conversion-focused CTAs. Use when asked to write, rewrite, optimize, or repurpose social posts for X/Twitter in a SaaS context.

X Post Creator

Overview

Generate concise SaaS-focused X posts that balance clarity, credibility, and conversion intent. Prioritize concrete value, specific proof, and one clear next action.

Workflow

  1. Collect missing context quickly. If not provided, infer a reasonable default and state assumptions. Capture: product, ICP, objective (awareness/trial/demo), offer, proof points, tone, and CTA.

  2. Choose one primary angle per post. Use references/angle-bank.md and avoid mixing multiple angles in one short post.

  3. Draft variants with pattern diversity. Use different templates from references/templates.md. Change sentence rhythm, opening style, and CTA language across variants.

  4. Enforce X constraints. Keep each post under 280 characters unless the user asks for a thread. Use plain language, avoid hype words, and remove filler.

  5. Run quality gate before finalizing. Check: clear hook in first line, concrete value, specific proof, single CTA, no repeated phrasing.

Output Format

For each post variant, return:

  • Post: final text ready to publish
  • Angle: chosen angle from the angle bank
  • Why it works: one short sentence

When useful, also include:

  • Alt CTA: one alternative CTA
  • Hashtags: 0-2 max, only if they add discoverability

Guardrails

  • Prefer specifics over adjectives (numbers, time saved, conversion lift, customer type).
  • Keep one post focused on one audience and one promise.
  • Avoid jargon density; if a term is niche, keep surrounding language simple.
  • Avoid overusing emojis, hashtags, and line breaks.
  • Never invent metrics or customer results; if missing, write without fake proof.

Adapting Requests

  • If asked for "more viral," increase novelty in the hook while preserving truthfulness.
  • If asked for "more technical," raise specificity but keep readability for busy founders/operators.
  • If asked for "rewrite," preserve core claim and CTA while changing structure and tone.
  • If asked for a thread, create a 5-7 post sequence with escalating detail and one CTA in the final post.

Resources

  • Use references/angle-bank.md to pick strategy by objective.
  • Use references/templates.md for fast drafting patterns.