القائمة
Run a maker outreach campaign through the orchestra. Use when sending claim emails, finding maker contacts, or expanding distribution to tool makers.
التثبيت باستخدام 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.
Write emails, social posts, and newsletter submissions for Your Project. Use when creating maker outreach, blog content, social media posts, or press pitches.
| name | outreach-batch |
| description | Run a maker outreach campaign through the orchestra. Use when sending claim emails, finding maker contacts, or expanding distribution to tool makers. |
| metadata | {"version":"2.0.0","author":"Master Agent","category":"distribution","updated":"2026-03-30T00:00:00.000Z"} |
You are managing a maker outreach campaign for Your Project. Your goal is to get tool makers to claim their listings, increasing engagement and moving toward revenue.
Check for context first:
Run all 6 steps below in order. Takes ~30 minutes with departments.
Skip to Step 1 with exclusions from previous batches. Reuse existing templates.
Check claim analytics, resend to non-responders with adjusted angle after 7 days.
SELECT slug, name, github_stars, url FROM tools
WHERE status='approved' AND maker_id IS NULL
AND github_stars > {threshold}
AND slug NOT IN ({already_emailed})
ORDER BY github_stars DESC LIMIT {count}
For each target, try in order:
gh api users/{owner} --jq '.email'gh api repos/{owner}/{repo} --jq '.owner.email'Expected hit rate: ~70%. Skip tools with no public email.
BEFORE sending, verify each tool page has:
Fix issues via Backend before proceeding.
Two template types:
Rules: under 80 words, from "Pat", include your-project.ai/claim/magic?tool={slug}, no upsell.
Send plan to Strategy before dispatching emails. S&QA checks:
await send_email(to=email, subject=subject, html_body=body)
Via ~/.fly/bin/fly ssh console -a your-project. Max 5 per call. 1s delay between.
Surface these WITHOUT being asked:
| Request | Deliverable |
|---|---|
| "Run outreach batch" | 15-20 personalized emails sent, /tmp/claim_emails_batch_N.md |
| "Find targets" | Slug + name + stars + email list |
| "Check responses" | Claim analytics from production DB |
| "Follow up" | Re-send with adjusted templates after 7 days |
-- instead