Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Pulse Weekly

ASecurity

Weekly community analysis report — aggregates Discord AND WhatsApp activity, engagement metrics, sentiment trends, top contributors, product insights, and docs gaps. Generates an HTML report using the Evolution brand. Use when user says 'weekly community', 'community analysis', 'weekly community report', or any reference to weekly community analysis.

529 stars
0 votes
0 copies
0 views
Added 5/29/2026
ai-agentspythongobashdocumentation

Works with

terminalcli

Security Analysis

A100/100

Scanned 5/29/2026

$npx -y skills add evolution-foundation/evo-nexus --skill pulse-weekly --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pulse Weekly?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Pulse Weekly
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/evolution-foundation-pulse-weekly/badge)](https://www.skillsdirectory.com/skills/evolution-foundation-pulse-weekly)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: pulse-weekly
description: "Weekly community analysis report — aggregates Discord AND WhatsApp activity, engagement metrics, sentiment trends, top contributors, product insights, and docs gaps. Generates an HTML report using the Evolution brand. Use when user says 'weekly community', 'community analysis', 'weekly community report', or any reference to weekly community analysis."
---

# Weekly Community Report

Weekly routine that analyzes Discord and WhatsApp activity from the last 7 days and generates a complete HTML report.

**Always respond in English.**

## Workflow

### Step 1 — Collect the week's data

Use the `/discord-get-messages` skill to fetch messages from the last 7 days in the main channels.

Guild ID: `YOUR_GUILD_ID`

Channels to monitor:
- All community text channels (chat-pt, chat-en, chat-es, help, feedback, suggestions, showcase, news)
- New members channel (`🆕・new-members`)

For each channel, fetch paginated messages (100 per request) to cover 7 days.

### Step 1b — Collect WhatsApp data (7 days)

Use the `/int-whatsapp` skill to fetch messages and stats from the last 7 days:

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

Include in the report as a separate "WhatsApp" section with: active groups, total messages, unique participants, topics, support questions.

### Step 2 — Calculate metrics

1. **Growth**: total members (estimate), new vs departed, net churn
2. **WAM (Weekly Active Members)**: unique members who sent a message
3. **Communicators**: % of visitors who chat (goal: 50%)
4. **Resolution rate**: answered questions / total in #help (goal: >80%)
5. **First response time**: median time between question and first response
6. **Messages per active member**: total msgs / WAM (goal: >4)

### Step 3 — Analyze sentiment and topics

For each day of the week:
1. **Sentiment**: classify messages as positive/neutral/negative
2. **Topics**: group discussions by theme, count frequency

Consolidate:
- Top 5 topics with sentiment bar
- Sentiment trend throughout the week

### Step 4 — Identify highlights

1. **Top 5 most active members**: by message volume + answers given
2. **New members who contributed**: who is new and already participated
3. **Members at risk of churn**: previously active, inactive this week

### Step 5 — Extract product insights

Analyze messages and identify:
1. **Most requested features**: spontaneous feature requests
2. **Reported bugs**: technical problems mentioned
3. **Docs gap**: questions whose answers should be in the documentation (indicate frequency)

### Step 6 — Comparison

If previous reports exist in `workspace/community/reports/weekly/`, compare:
- WAM this week vs previous
- New members vs previous
- Resolution rate vs previous
- Response time vs previous

### Step 7 — Generate HTML report

Read the template at `.claude/templates/html/custom/community-weekly-report.html`.

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

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

Save to:
```
workspace/community/reports/weekly/[C] YYYY-WXX-community-report.html
```

### Step 8 — Executive summary

Present in the terminal:

```
## Weekly Report — Week {WXX}

Members: {N} ({+/-}) | WAM: {N} ({X}%)
Resolution: {X}% | 1st response: {X} min
Sentiment: {label}
Top: {topic 1}, {topic 2}, {topic 3}
Insights: {N} features, {N} bugs, {N} docs gaps

Report saved to workspace/community/reports/weekly/
```

## Rules

- **Do not reply to messages** — only read and analyze
- **Real data** — metrics based on collected messages, no fabrication
- **Docs gap is gold** — each question without docs becomes a backlog item
- **Comparison is fundamental** — always show trend vs previous week
- **Product insights** — the most valuable section, handle with care

Attribution

evolution-foundationevolution-foundation
View sourceSee grades on GitHubMore from evolution-foundation →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →