smartworldarafath/rea_skill

investor-outreach

Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/smartworldarafath/rea_skill --skill investor-outreach

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Investor Outreach

Write investor communication that is short, concrete, and easy to act on.

When to Activate

  • writing a cold email to an investor
  • drafting a warm intro request
  • sending follow-ups after a meeting or no response
  • writing investor updates during a process
  • tailoring outreach based on fund thesis or partner fit

Core Rules

  1. Personalize every outbound message.
  2. Keep the ask low-friction.
  3. Use proof instead of adjectives.
  4. Stay concise.
  5. Never send copy that could go to any investor.

Voice Handling

If the user's voice matters, run brand-voice first and reuse its VOICE PROFILE. This skill should keep the investor-specific structure and ask discipline, not recreate its own parallel voice system.

Hard Bans

Delete and rewrite any of these:

  • "I'd love to connect"
  • "excited to share"
  • generic thesis praise without a real tie-in
  • vague founder adjectives
  • begging language
  • soft closing questions when a direct ask is clearer

Cold Email Structure

  1. subject line: short and specific
  2. opener: why this investor specifically
  3. pitch: what the company does, why now, and what proof matters
  4. ask: one concrete next step
  5. sign-off: name, role, and one credibility anchor if needed

Personalization Sources

Reference one or more of:

  • relevant portfolio companies
  • a public thesis, talk, post, or article
  • a mutual connection
  • a clear market or product fit with the investor's focus

If that context is missing, state that the draft still needs personalization instead of pretending it is finished.

Follow-Up Cadence

Default:

  • day 0: initial outbound
  • day 4 or 5: short follow-up with one new data point
  • day 10 to 12: final follow-up with a clean close

Do not keep nudging after that unless the user wants a longer sequence.

Warm Intro Requests

Make life easy for the connector:

  • explain why the intro is a fit
  • include a forwardable blurb
  • keep the forwardable blurb under 100 words

Post-Meeting Updates

Include:

  • the specific thing discussed
  • the answer or update promised
  • one new proof point if available
  • the next step

Quality Gate

Before delivering:

  • the message is genuinely personalized
  • the ask is explicit
  • the proof point is concrete
  • filler praise and softener language are gone
  • word count stays tight
同じリポジトリから

関連する Skills

すべての Skills
smartworldarafath
コミュニティ

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

1時間の導入数
2
GitHub Stars
5
更新日
11月8日
smartworldarafath
コミュニティ

agent-reach

Read-only access to internet platforms (Twitter/X, Reddit, YouTube subtitles, GitHub, LinkedIn, Bilibili, web). Use when the agent needs to search, read web links, retrieve social discussions, CVE/vulnerability intel, or when standard web search/fetch is blocked or insufficient.

1時間の導入数
2
GitHub Stars
5
更新日
11月8日
smartworldarafath
コミュニティ

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

1時間の導入数
2
GitHub Stars
5
更新日
11月8日
smartworldarafath
コミュニティ

anti-ai-slop-writing

Produces human-sounding text that avoids detectable AI writing patterns. Activates on any writing task — tweets, emails, articles, bios, captions, reports, copy, messages, LinkedIn posts, cover letters, README files, or any content where the output must not read as AI-generated. Enforces banned vocabulary, structural variety, punctuation discipline, accuracy rules, and voice calibration. Use when the user says "write," "draft," "rewrite," "make this sound human," "anti-slop," "not AI," or any va

1時間の導入数
2
GitHub Stars
5
更新日
11月8日