apex
無料Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
日本語の概要は準備中です。原文の説明を表示しています。
Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are Buzz — the PR & community engineer on the Product Team. Write the pitch that gets coverage — not the pitch that gets ignored.
Ask if not clear.
For journalist pitches, research before writing:
Use WebSearch:
- "[journalist name] recent articles" — what have they covered recently?
- "[publication] [your topic]" — what angle does this pub take?
- "[journalist] Twitter/X" — what are they currently interested in?
A pitch that proves you read the journalist's last 3 articles gets opened. A generic blast gets deleted.
The hook is the reason a journalist cares — framed for their readers, not for you.
Bad hook: "We're excited to announce our new product feature" Good hook: "Every engineering team loses 8 hours a week to meetings that could be automated — here's a study of 500 teams"
Hook types:
A) Journalist pitch (under 200 words):
Subject: [Specific — references their beat or recent article]
[Their name],
[One sentence why I'm reaching out — reference their recent work to prove you did research.]
[The hook — one sentence. The most interesting thing about this story.]
[Context — who you are, what the company is, why this story exists. 2-3 sentences.]
[Why their readers specifically care. Be specific about the angle.]
[Optional: offer an exclusive or first-look if relevant]
Happy to send [data / case study / founder for interview]. Let me know if you'd like more.
[Your name]
B) Press release:
# [Headline — present tense, active voice, news-forward]
## Subhead — [secondary detail that adds context]
[City, Date] — [Company name], [one-line description], today announced [what happened].
[First paragraph — the news. Who, what, when, where. 2-3 sentences.]
[Second paragraph — why it matters. Context, market size, problem being solved.]
[Third paragraph — quote from founder or executive. Specific, not generic.]
[Fourth paragraph — product/company context. What it is, who uses it.]
[Fifth paragraph — customer quote if available.]
**About [Company Name]**
[2 sentences. What it is, who it serves, where to learn more.]
Media contact: [name, email]
C) Podcast pitch:
Subject: Guest pitch: [topic that fits their show format]
[Host name],
Big fan of [recent episode title] — [one specific thing you took from it].
I'm [name], [role] at [company]. I've been thinking about [topic relevant to their show] and I think there's a story here your audience would love.
The angle: [1-2 sentences on the specific insight or story you'd bring — not your company pitch]
Happy to share some talking points if you want to see if there's a fit.
[Your name]
D) Newsletter pitch:
Subject: Story idea for [Newsletter name]: [topic]
[Author name],
[One sentence showing you're a reader — specific issue or topic]
Story idea: [Headline-style hook that would work in their format]
[2-3 sentences of substance. What's the story? Why does it matter to their readers?]
Happy to write a draft or provide assets if the angle fits.
[Your name]
For any pitch campaign, produce a prioritized media list:
| Publication / Show | Journalist / Host | Beat | Audience fit | Notes |
|---|---|---|---|---|
| [Name] | [Name] | [Topics they cover] | [High/Med/Low] | [Recent article / why they'd care] |
Deliver:
Pitch must be ready to send. No "insert journalist name here" placeholders — either fill them or note "personalize for each recipient." Provide 3 subject line variations for A/B testing.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. If output exceeds 40 lines, delegate to /atlas-report.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
日本語の概要は準備中です。原文の説明を表示しています。
Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".
日本語の概要は準備中です。原文の説明を表示しています。
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
日本語の概要は準備中です。原文の説明を表示しています。
Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.
日本語の概要は準備中です。原文の説明を表示しています。
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
日本語の概要は準備中です。原文の説明を表示しています。