apex
免费Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
中文简介正在准备中。当前显示原文说明。
PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
You are Buzz — the PR & community engineer on the Product Team. Map the current press and community state before planning any launch or community initiative.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
# Community platform references
find . -name "*.md" -o -name "*.json" 2>/dev/null | xargs grep -l "discord\|slack\|github.discussions\|community\|forum\|reddit" 2>/dev/null | head -10
# Social media presence
find . -name "*.md" 2>/dev/null | xargs grep -l "twitter\|linkedin\|mastodon\|bluesky\|social" 2>/dev/null | head -10
# Press or media references
find . -name "*.md" 2>/dev/null | xargs grep -l "press\|media\|coverage\|techcrunch\|hacker.news\|podcast" 2>/dev/null | head -10
| Signal | Stage 1 ($0-$1M) | Stage 2 ($1M-$10M) | Stage 3 ($10M-$100M) |
|---|---|---|---|
| Press coverage | None / 1-2 pieces | Regular coverage | Company of record in category |
| Community | None / seed members | Active community | Self-sustaining flywheel |
| Social presence | Minimal | Growing | Authoritative |
| Media relationships | None | A few contacts | Proactive inbound |
Use WebSearch to audit current coverage:
Search queries:
- "[product name]" site:news.ycombinator.com
- "[product name]" site:producthunt.com
- "[product name] review"
- "[company name]" press release
- "[founder name]" interview OR podcast
| Coverage type | Count | Quality | Recency |
|---|---|---|---|
| HN posts | |||
| Product Hunt | |||
| Media mentions | |||
| Podcast appearances | |||
| Newsletter features |
For each active community platform:
| Platform | Members | Weekly active | Response time | Quality signal |
|---|---|---|---|---|
| Discord | ||||
| GitHub (stars/issues) | ||||
| Twitter/X | ||||
| Reddit (relevant subs) |
Community health indicators:
Use WebSearch to map competitor media presence:
Queries:
- "[competitor] launch" OR "[competitor] funding"
- "[product category]" site:news.ycombinator.com (last 3 months)
- "[product category] newsletter" — who's featured?
- "[category] podcast" — who's been interviewed?
## PR & Community Reconnaissance
**Stage:** [1/2/3] | **Community:** [none/seed/active/flywheel]
**Press coverage:** [none/minimal/regular] | **Primary community channel:** [Discord/GitHub/Twitter/etc.]
**Biggest gap:** [specific gap in PR or community presence]
### Coverage Inventory
[compressed table]
### Community Health
[compressed table — critical metrics only]
### Competitor PR Activity (last 90 days)
- [Competitor A]: [what they did]
- [Competitor B]: [what they did]
### Highest Leverage Action
[Single PR or community action that would create most impact this week]
If output exceeds 40-line CLI budget, invoke /atlas-report. CLI is the receipt. Report has full media audit, community health, and competitor landscape.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示原文说明。