This is a coordinator that monitors your GitHub community health and decides whether you need to announce features, respond to stale discussions, or launch an RFC debate. It runs discovery to map your repo structure, checks what's unreleased since your last announcement, applies a priority matrix (P0 for unanswered discussions over seven days, P1 for unreleased changelog entries), then delegates to one of four worker skills: a triager, announcer, debater, or responder. The strategy is configurable per project. Use it when you want systematic community management instead of ad hoc responses, or when you're not sure which engagement task should happen next. The situational analysis before delegation is the clever bit here.
npx -y skills add levnikolaevich/claude-code-skills --skill ln-910-community-engagement --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
juliusbrussee/caveman
mattpocock/skills
shadcn/improve
obra/superpowers
forrestchang/andrej-karpathy-skills
vercel-labs/skills