community-pulse — Claude Code skill: what it does, how to install
Produces a weekly community digest from Discord, Crisp chats, and YouTube comments. It spots membership changes, trending topics, and unresolved questions.
npx skills add cognyai/claude-code-marketing-skills --skill community-pulse -a claude-codeWhat community-pulse does
This skill scans community platforms through Cogny's MCP gateway to prepare a weekly summary. Discord serves as the primary data point. The assistant tracks member arrivals over the last seven days, measures week-over-week growth, and flags days with more than 40% of new signups. If Crisp and YouTube connections exist, it pulls open support dialogs and unaddressed video comments alongside guild metrics.
Processing stays capped at 30 channels to manage run time. Voice channels and plain categories are ignored. Private channels receive separate handling: the skill measures overall message counts and broad themes, but strips out member names and direct quotations. When follow-ups are needed, it logs findings or tickets via Cogny tooling.
Operation relies on the Cogny HTTP gateway in .mcp.json. Without Server Members Intent and Message Content Intent enabled in the Discord Developer Portal, member listings return empty and message bodies come back blank. The bot also requires explicit permissions to view channels and read message logs.
What it helps with
- track weekly Discord member acquisition and week-over-week changes
- detect unresolved customer questions across Discord channels and Crisp support chats
- highlight message volume surges and recurring discussion topics
- review unaddressed YouTube comment threads in a single report
Example prompts for the agent
- /community-pulse
- /community-pulse 123456789012345678
- Generate a weekly digest of our Discord server using /community-pulse
How to install community-pulse
1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill community-pulse -a claude-code2Manually: put the files in place
~/.claude/skills/community-pulse/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/community-pulse/
1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill community-pulse -a codex2Manually: put the files in place
.agents/skills/community-pulse/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill community-pulse -a cursor2Manually: put the files in place
.cursor/skills/community-pulse/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cognyai/claude-code-marketing-skills community-pulse2Manually: put the files in place
.github/skills/community-pulse/SKILL.md1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill community-pulse -a gemini-cli2Platform CLI
gemini skills install https://github.com/cognyai/claude-code-marketing-skills --path skills/community-pulseManually: put the files in place
.devin/skills/community-pulse/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill community-pulse -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about community-pulse
How do I install community-pulse in Claude Code?
Run npx skills add cognyai/claude-code-marketing-skills --skill community-pulse -a claude-code. You can also place the configuration file directly at ~/.claude/skills/community-pulse/SKILL.md.
What does community-pulse do?
It generates a weekly status report on community activity across Discord, Crisp conversations, and YouTube channels. The output covers member influx, active discussion themes, and unanswered queries.
What permissions does community-pulse require on Discord?
You must turn on Server Members Intent and Message Content Intent in the Discord Developer Portal. The bot also needs channel permissions to view channels and inspect message history.
