Agent skill · Code Review & Quality

whatsapp-logs

Read and analyze WhatsApp bot logs for debugging, monitoring, and troubleshooting. Use this skill when asked to "check WhatsApp logs", "debug the bot", "find WhatsApp errors", "analyze bot performance", "trace a message", "why did the bot fail", or any investigation of WhatsApp bot behavior. Covers log file locations, JSON log format, message tracing, error analysis, and common debugging patterns.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill whatsapp-logs --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/analysis/whatsapp-logs/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# WhatsApp Bot Log Analysis ## Log Files | File Pattern | Purpose | | ------------------------------------ | -------------------------------- | | `logs/whatsapp-debug-YYYY-MM-DD.log` | All WhatsApp bot activity (JSON) | | `logs/whatsapp-error-YYYY-MM-DD.log` | WhatsApp errors only | Get today's logs: ```bash ls -la logs/whatsapp-*.log 2>/dev/null | tail -5 ``` ## JSON Log Structure ```json { "timestamp": "2026-01-04 14:30:45.123", "level": "INFO", "message": "Received message", "service": "whatsapp", "correlationId": "550e8400-e29b-41d4-a716-446655440000", "operation": "handleMessage", "durationMs": 1234, "meta": { "from": "972501234567", "isGroup": false, "textPreview": "What's in progress?" } } ``` **Key Fields:** - `service` - Always "whatsapp" for bot logs - `correlationId` - UUID linking logs for a single request - `operation` - What operation was performed - `durationMs` - Time taken in milliseconds - `meta.from` - Sender phone number - `meta.isGroup` - Whether message came from a group ## Quick Commands ### View Recent Activity ```bash tail -50 logs/whatsapp-debug-$(date +%Y-%m-%d).log | jq . ``` ### Check Errors Today ```bash cat logs/whatsapp-error-$(date +%Y-%m-%d).log 2>

What's inside
Steps it walks through
  1. Log Files
  2. JSON Log Structure
  3. Quick Commands
  4. View Recent Activity
  5. Check Errors Today
  6. Watch Logs Real-Time
  7. Find Messages From a Phone Number
  8. Check Connection Status
  9. Common Debugging Scenarios
  10. Bot Not Responding
  11. Connection Issues
  12. Voice Message Issues
  13. Group Message Issues
  14. Image Processing Issues
Ships with 1 file
  • metadata.json
Commands it runs
ls -la logs/whatsapp-*.log 2>/dev/null | tail -5
tail -50 logs/whatsapp-debug-$(date +%Y-%m-%d).log | jq .
cat logs/whatsapp-error-$(date +%Y-%m-%d).log 2>/dev/null | jq .
tail -f logs/whatsapp-debug-$(date +%Y-%m-%d).log | jq .
grep '"from":"972501234567"' logs/whatsapp-debug-*.log | jq .
grep -E "(Connected|Disconnected|reconnect)" logs/whatsapp-debug-*.log | tail -10 | jq .
Check if messages are being received
grep "Received message" logs/whatsapp-debug-$(date +%Y-%m-%d).log | tail -5 | jq '{time: .timestamp, from: .meta.from, text: .meta.textPreview}'
Check for processing errors
grep -E '"level":"ERROR"' logs/whatsapp-debug-$(date +%Y-%m-%d).log | tail -10 | jq .
More from claude-skill-registry
All skills →
About this skill
What does the whatsapp-logs skill do?

Read and analyze WhatsApp bot logs for debugging, monitoring, and troubleshooting. Use this skill when asked to "check WhatsApp logs", "debug the bot", "find WhatsApp errors", "analyze bot performance", "trace a message", "why did the bot fail", or any investigation of WhatsApp bot behavior. Covers log file locations, JSON log format, message tracing, error analysis, and common debugging patterns.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill whatsapp-logs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going