@criptogus/community-engagement
BUse when planning programs, rituals, and response frameworks for owned
Install
agr install @criptogus/community-engagement --target claudeWrites 1 file into .claude/skills/, pinned to git-d1eaa09d.
- .claude/skills/community-engagement/SKILL.md
Document
name: community-engagement description: Use when planning programs, rituals, and response frameworks for owned or partner communities.
Community Engagement Patterns Skill
When to Use
- Launching or refreshing Slack/Discord/Facebook/LinkedIn communities.
- Designing ambassador, influencer, or creator enablement programs.
- Handling sentiment spikes (positive or negative) tied to social content.
Framework
Engagement Building Blocks
- Rituals – recurring AMAs, demo days, office hours, wins threads.
- Spotlights – member highlights, case study showcases, creator takeovers.
- Challenges – thematic prompts with templates, prizes, referral boosts.
- Feedback Loops – polls, surveys, beta access, roadmap Q&As.
Program Playbook
- Define success metrics (active members, participation %, referral pipeline).
- Assign moderation tiers and escalation paths.
- Create template library (welcome flows, DM scripts, escalation responses).
- Sync weekly with product/support to triage insights.
Response Framework
- Listen – capture sentiment, metadata, severity.
- Acknowledge – respond publicly if appropriate, move to DMs when sensitive.
- Resolve – collaborate with support/product/legal.
- Document – log issue + resolution to inform future programming.
Templates
- Community health dashboard template.
- Ambassador enablement kit.
- Crisis response matrix (severity ladder + owner by stage).
- Welcome/onboarding message pack with DM + channel scripts.
Tips
- Publish a weekly wins digest to reinforce positive behavior and keep leadership informed.
- Maintain an escalation log so repeat issues inform new rituals or automations.
- Rotate moderators quarterly to prevent burnout and keep tone aligned with evolving brand voice.
- Pair community programming with GTM launches (betas, AMAs) to reinforce ROI.
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-d1eaa09df4d52026-07-31