SuperAPI AI Directory

@1892/crypto-content

Writing & research

View repository

Updated 10-16 09:31

About this skill

Crypto Content Writer

Write professional content for crypto project announcements and communications.

When to Use

  • Writing blog posts or articles for a crypto project
  • Creating tweet threads for social accounts
  • Drafting announcements (product launches, partnerships, upgrades)
  • Educational content explaining mechanisms or features
  • Any content representing a crypto brand

What to Ask For Upfront

If not provided, ask for:

  1. Project name and what it does (one sentence)
  2. Brand voice (calm/technical? energetic? institutional?)
  3. Audience (traders, developers, DeFi users, general crypto?)
  4. Content type (announcement, explainer, thread, full article)

Default Brand Voice

Calm, confident, technically precise. Never hype-y or desperate. Lead with the problem, then the solution. Explain technical concepts simply without dumbing down. Respect the reader's intelligence.

Adapt tone to the brand when provided — but always stay human.

Critical Style Rules

Write like a human, not like AI:

  • No short, choppy sentences that feel robotic
  • Combine related ideas into flowing sentences that move naturally
  • Never use em dashes (AI tell) — use commas, parentheses, or restructure
  • Never use horizontal dividers (---) between sections
  • No hype words: "exciting," "thrilled," "game-changing," "revolutionary"
  • No emojis in articles (tweet threads can have one or two)

Article Structure

Open with a bold TL;DR (one or two sentences capturing the core insight). Then move through:

  1. Problem — why the reader should care
  2. Solution — what's changing and how it works
  3. Outcome — benefits and timeline

Don't pad sections to look substantial. A two-sentence section is fine if that's all it takes.

Tweet Threads

Maximum 3 tweets unless specifically requested longer:

  1. Hook — the problem and why it matters
  2. Solution — mechanism + what makes it different
  3. Outcome — timeline + impact + optional link

No hashtags. Tag partners with @. Short enough to scan, not so choppy they feel robotic.

Output Format

Always deliver both:

  1. Article — formatted with headers, ready to paste into any CMS or Notion
  2. Tweet thread — numbered, copy-paste ready

Quality Checklist

Before delivering: problem stated clearly, technical concepts explained, no hype words, no em dashes, no horizontal dividers, active voice, flowing sentences, tweet thread 3 or fewer, concrete timeline mentioned, partner tags correct.

References

Load on demand: