buzz-recon
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "buzz-recon":https://skillpi.com/zh/skills/deepskill-7c3d181351b88a648087149af05e39e759e457c09d9e37a5c7df6da5216843f9。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/buzz-recon/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/buzz-recon --skill buzz-recon来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“buzz-recon”,按来源分类归入「运营社媒账号」使用场景、「市场与营销」职业。目录标签:ai-lab、公关、社群、媒体。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: buzz-recon description: 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. allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.1.0 author: tonone-ai <hello@tonone.ai> license: MIT --- # PR & Community Reconnaissance 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. ## Steps ### Step 0: Find Community Artifacts ```bash # 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 ``` ### Step 1: Diagnose PR Stage | 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 | ### Step 2: Press Coverage Inventory 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 | | | | ### Step 3: Community Health Audit For each active community platform: | Platform | Members | Weekly active | Response time | Quality signal | | ---------------------- | ------- | ------------- | ------------- | -------------- | | Discord | | | | | | GitHub (stars/issues) | | | | | | Twitter/X | | | | | | LinkedIn | | | | | | Reddit (relevant subs) | | | | | Community health indicators: - Are users helping other users? (not just asking questions) - Is there user-generated content? (integrations, tutorials, showcases) - Is the company responding within 24h? - Are there power users / ambassadors emerging? ### Step 4: Competitor PR Landscape 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? ``` ### Step 5: Present Assessment ``` ## 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] ``` ## Delivery If output exceeds 40-line CLI budget, invoke `/atlas-report`. CLI is the receipt. Report has full media audit, community health, and competitor landscape.
当前收录版本
0.1.0
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供完整的公关与社区侦察闭环流程,覆盖媒体、社区、竞品三大维度
评分依据
触发词覆盖多种变体(如“审核公关”、“社区现状”、“媒体表现”),边界清晰
评分依据
步骤划分清晰(Step 0-5),逻辑连贯
评分依据
工具使用合理(WebSearch、Read、Bash 等),参数正确
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。