Agent skill

pulse-daily

Daily community pulse report — reads Discord AND WhatsApp messages from the last 24h, analyzes activity, sentiment, support questions, and top topics. Generates an HTML report using the Evolution brand. Use when user says 'community pulse', 'daily community report', or any reference to daily community health check.

Stars 211
Forks 54

Install this agent skill to your Project

npx add-skill https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/pulse-daily

SKILL.md

Daily Community Pulse

Daily routine that reads Discord and WhatsApp messages from the last 24h and generates an HTML community health report.

Always respond in English.

Workflow

Step 1 — Collect Discord data

Use the /discord-get-messages skill to fetch messages from the last 24h in the main channels:

Channels to monitor (Guild ID: YOUR_GUILD_ID):

  • 💬・chat-pt — chat principal PT
  • 💬・chat-en — chat principal EN
  • 💬・chat-es — chat principal ES
  • 🆘・help — suporte
  • 🆘・feedback — feedback
  • 💡・suggestions — suggestions
  • 💎・showcase — showcase
  • 📢・news — news

For each channel, fetch the last 100 messages and filter those from the last 24h.

Step 1b — Collect WhatsApp data

Use the /int-whatsapp skill to fetch messages from the last 24h:

bash
python3 {project-root}/.claude/skills/int-whatsapp/scripts/whatsapp_client.py messages_24h

And also the statistics:

bash
python3 {project-root}/.claude/skills/int-whatsapp/scripts/whatsapp_client.py stats --start $(date -u -v-1d '+%Y-%m-%d') --end $(date -u '+%Y-%m-%d')

Extract: total messages, active groups, unique participants, discussed topics, support questions.

Step 2 — Analyze

From the collected messages, calculate:

  1. Activity: total messages (Discord + WhatsApp separate), unique active members, most active channel/group
  2. New members: check 🆕・new-members for entries today
  3. Support: unanswered questions in 🆘・help (Discord) + questions in WhatsApp groups, time without response
  4. Sentiment: analyze the overall tone (positive/neutral/negative) based on content from both platforms
  5. Top topics: group by theme the most frequent discussions from Discord + WhatsApp (maximum 6)
  6. WhatsApp: active groups, total messages, unique participants, topics — separate section in the report
  7. Overall health: Normal (>80% positive, <3 open questions), Attention (mixed sentiment or 3-5 open questions), Critical (negative sentiment or >5 unanswered questions)

Step 3 — Generate HTML report

Read the template at .claude/templates/html/custom/community-daily-pulse.html.

Replace the placeholders {{...}} with the actual collected data.

Evolution logo available at: workspace/projects/Evolution Foundation/Logos finais/Favicon logo/SVG/Favicon Color 500.svg

Save the filled HTML to:

workspace/community/reports/daily/[C] YYYY-MM-DD-community-pulse.html

Create directory if it does not exist.

Step 4 — Terminal summary

Present a short summary in the terminal:

## Daily Pulse — {date}

Health: {Normal/Attention/Critical}
Messages: {N} | Active: {N} | New: {N}
Support: {N} unanswered
Sentiment: {emoji} {label}
Top: {topic 1}, {topic 2}, {topic 3}

Report saved to workspace/community/reports/daily/

Rules

  • Do not reply to messages on Discord — only read and analyze
  • Sentiment based on real content — do not guess, analyze the messages
  • Unanswered questions = priority — always highlight
  • Compare with average — if previous reports exist in the directory, compare metrics
  • Empty channels = OK — if a channel had no activity, do not report as a problem

Notify via Telegram

Upon completion, send a short summary via Telegram to the user:

  • Use the Telegram MCP: reply(chat_id="YOUR_CHAT_ID", text="...")
  • Format: emoji + routine name + main result (1-3 lines)
  • If the routine had no updates, send anyway with "no updates"

Expand your agent's capabilities with these related and highly-rated skills.

EvolutionAPI/evo-nexus

data-create-viz

Cria visualizações de dados de qualidade profissional com Python no tema Evolution (fundo escuro, acento

211 54
Explore
EvolutionAPI/evo-nexus

cs-customer-escalation

Empacota uma escalação para Devs, Produto ou Davidson com contexto completo. Use quando um bug precisa de atenção além do suporte normal, vários clientes reportam o mesmo problema, um cliente está ameaçando cancelar, ou um problema ficou sem resolução além do SLA. / Package an escalation for engineering, product, or leadership with full context. Use when a bug needs engineering attention beyond normal support, multiple customers report the same issue, a customer is threatening to churn, or an issue has sat unresolved past its SLA.

211 54
Explore
EvolutionAPI/evo-nexus

mkt-draft-content

Draft blog posts, social media, email newsletters, landing pages, press releases, and case studies with channel-specific formatting and SEO recommendations. Use when writing any marketing content, when you need headline or subject line options, or when adapting a message for a specific platform, audience, and brand voice.

211 54
Explore
EvolutionAPI/evo-nexus

gog-tasks

Create, manage, and prioritize tasks and todo items. Convert emails to tasks, set priorities (P0-P3) and categories (Work/Personal/Errands/Admin), review daily priorities, track blocked and overdue tasks. Use when user mentions tasks, todos, action items, or wants to convert emails to tasks. Requires confirmation before creating or deleting tasks.

211 54
Explore
EvolutionAPI/evo-nexus

discord-get-messages

Retrieve messages from Discord channels via the Discord API. Use this skill when the user wants to read, search, or analyze messages from a Discord channel.

211 54
Explore
EvolutionAPI/evo-nexus

cs-customer-research

Pesquisa multi-fonte sobre pergunta ou tópico de cliente com atribuição de fontes. Use quando um cliente pergunta algo que precisa ser verificado, investigando se um bug foi reportado antes, verificando o que foi dito anteriormente a uma conta específica, ou coletando contexto antes de redigir uma resposta. / Multi-source research on a customer question or topic with source attribution. Use when a customer asks something you need to look up, investigating whether a bug has been reported before, checking what was previously told to a specific account, or gathering background before drafting a response.

211 54
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results