القائمة
Analyze configured customer Slack channels and produce temporary customer-channel analysis context for later share-recommendation workflows.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Draft concise, Slack-ready internal announcement messages from the latest <BRAND> changelog, focused on major shipped features and verified external-contributor highlights. Use this when the user asks for a changelog announcement, weekly shipped summary, internal Slack launch/update post, external community contribution highlights, or asks to turn recent <BRAND> changelog entries into a short message for Slack.
Weekly skill that scans merged PRs in your internal repo for CHANGELOG entries, categorizes them into topic buckets, drafts tweet suggestions, and posts a structured summary to #social-swarm on Slack for the team to pick up. Use when asked to "generate the social swarm post", "what's tweet-worthy this week", or "run the changelog bot".
Create customer-channel share recommendations by having an agent compare customer-channel analysis with recent brand content and Slack history.
End-of-day recap of <BRAND>'s social mentions using Octolens. Produces a Slack-ready summary with sentiment score, highlights, and lowlights. Use when the user asks for a daily mentions recap, EOD summary, or "what happened today in mentions".
Daily discovery of viral and rising X posts relevant to <BRAND>'s product and <PRODUCT_CATEGORY>. Searches curated thought leader feeds, filters for relevance first, then ranks by engagement. Surfaces top posts to #social-swarm with engagement recommendations. Use when the user asks for a "viral post roundup", "what's trending in <PRODUCT_CATEGORY>", "social swarm digest", or "find posts to engage with".
Brainstorm and evaluate X article title options for an author based on a Google Doc draft and an initial title idea. Uses the author's historical engagement data to score angles. Trigger when the user shares a Google Doc URL and wants title ideas, says "brainstorm titles", "help with an article title", "what should I call this", or "weigh this title against options". Always use this skill when a gdoc + title question appear together.
| name | customer-channel-analysis |
| description | Analyze configured customer Slack channels and produce temporary customer-channel analysis context for later share-recommendation workflows. |
Use this skill to understand what is happening in configured customer Slack channels: recurring themes, adoption friction, active customer people, sensitivities, and follow-up/content opportunity themes.
From the Buzz root, collect and format the analysis input:
python3 .agents/skills/customer-channel-analysis/scripts/run_analysis.py --days 180
The command writes temporary prep files under /tmp/customer-channel-analysis/. Read the formatted analysis input, then create the temporary analysis outputs in the same directory.
For each run, keep the analysis outputs under /tmp/customer-channel-analysis/:
/tmp/customer-channel-analysis/customer-channel-analysis-<start-YYYY-MM-DD>-to-<end-YYYY-MM-DD>.md
/tmp/customer-channel-analysis/customer-channel-analysis-<start-YYYY-MM-DD>-to-<end-YYYY-MM-DD>.json
The Markdown file is the human report. The JSON file is the structured analysis output for downstream workflows.
Do not store raw Slack exports, full transcripts, copied Slack message excerpts, or generated analysis artifacts in data/ unless the user explicitly asks for a durable report. Keep Slack message content in Slack; downstream workflows can use Slack links and make API calls when they need source context.
Keep the report concise and high-signal:
Use inline Slack links as evidence. Do not paste message bodies or collect supporting links in a separate appendix.
The JSON output should contain curated analysis, not message history:
Evidence objects should keep fields such as slack_url, channel_id, message_ts, thread_ts, message_datetime, and speaker_side when known. Do not include message text excerpts or customer names unless they are necessary and already present in the human report.