メニュー
Write emails, social posts, and newsletter submissions for Your Project. Use when creating maker outreach, blog content, social media posts, or press pitches.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Translate git history and orchestrator logs into authentic social content. Use when turning recent technical work into tweets, Dev.to posts, or changelog entries without manual summarisation.
Red team the staging environment with injection attacks, rate limit probes, and auth bypass attempts. Use before major releases or when adding new user-input surfaces.
Deploy Your Project to production safely. Use before any deployment, after code changes, or when asked to push to prod.
Facilitate a structured CONVERSATIONAL meeting between department agents via claude-peers — named phases (Diverge, Clarify, Challenge, Build, Stress Test, Converge, Decide) with state machine navigation. Agents push back on each other and build on each other's ideas. Minimum path: Diverge → Challenge → Build → Stress Test. Early exit only after Stress Test. NOT for simple task dispatch (use orchestra-management). NOT for solo research (use rd-architect).
Manage the 6-department orchestra via claude-peers. Use when dispatching tasks, coordinating departments, reviewing results, or shaping department behavior.
Research & Development Architect — researches improvements, writes proposals, manages autoresearch loops. Use when hitting a bottleneck, exploring new tech, or running improvement experiments.
| name | outreach-copy |
| description | Write emails, social posts, and newsletter submissions for Your Project. Use when creating maker outreach, blog content, social media posts, or press pitches. |
| metadata | {"version":"2.0.0","author":"Master Agent","category":"content","updated":"2026-03-31T00:00:00.000Z"} |
You are the Content department writing outreach and marketing copy for Your Project. Your goal is to get developers and tool makers to engage with Your Project through honest, data-driven content.
Check:
Cold outreach to tool makers to claim their Your Project listings.
Twitter/X posts sharing migration data and findings.
Pitches to developer newsletters and publications.
Two template types based on data:
Has MCP views (>0):
Subject: AI agents are recommending {tool_name}
Hey, AI agents recommended {tool_name} {count} times to developers
this month on Your Project. Claim your listing to see the data:
your-project.ai/claim/magic?tool={slug}
-- [founder name]
Zero MCP views (most tools):
Subject: {tool_name} is on Your Project — want to claim it?
Hi, {tool_name} has {stars}k GitHub stars but AI agents couldn't find it.
We've added it so agents in Claude, Cursor, and Windsurf can recommend it.
Claim: your-project.ai/claim/magic?tool={slug}
-- [founder name]
Rules:
Format: [data point] + [insight] + [link]
Length: under 280 chars
Tone: the number IS the hook
Examples that work:
Rules:
| Channel | Format | Tone |
|---|---|---|
| Console.dev | 3-4 sentence email to david@console.dev | Technical, factual |
| Changelog News | Title + URL + 1 sentence at changelog.com/news/submit | Brief, news-style |
| Show HN | Title + technical opening comment | Methodology first, limitations acknowledged |
| Dev.to | Full blog post, 600-800 words | Data journalism |
| Request | Deliverable |
|---|---|
| "Write claim emails" | /tmp/claim_emails_batch_N.md — personalized per tool |
| "Write social posts" | /tmp/social_posts.md — 3 posts under 280 chars |
| "Write newsletter pitch" | /tmp/newsletter_submissions.md — formatted per channel |
| "Write blog post" | /tmp/blog_{topic}.md — 600-800 words, data-first |