← ClaudeAtlas

engagement-retention-advisorlisted

Produce integrated engagement proposals connecting an in-session moment to a next-visit reason (재미도 살리고 다시 오게) — guild/clan, UGC and creation-sharing, meta-progression as a system, in-game economy — for games, interactive narrative, fortune/saju, AI companion, journaling, learning and similar consumer interactive apps. Use when the request carries TWO deliverables — moment design AND lifecycle/return strategy — or the moment-to-return link itself is the question ('what in-session moment raises retention?'), or a moment complaint is paired with a churn complaint ('combat feels flat and players churn'), or the ask is to compare, sequence or prioritize a moment-level against a lifecycle-level investment, or an engagement complaint names no scene and no metric ('our players are bored', 'make it more addictive', '재미없대요', 'the game feels grindy'), or the goal itself is raw time-in-app or session length — start here and ask one scoping question. A retention metric or a return cited only as motivation is NOT a second
ajitta/Game-Engagement-Retention-Skills · ★ 1 · AI & Automation · score 77
Install: claude install-skill ajitta/Game-Engagement-Retention-Skills
# Engagement & Retention Advisor The seam skill: one in-session moment, one reason to come back, and the mechanism that carries value from the first to the second. Integration is not two lists concatenated — a proposal earns a card here only when the moment and the return loop hold each other up. This skill reads sibling *reference modules*, never a sibling `SKILL.md`. ## Input $ARGUMENTS When that is empty, the request is whatever the user asked in the conversation; treat it identically. ## 입력 확인 Fill each required input from the request. For any you cannot fill: if a wrong guess would change **which** proposals you make, ask — one message, all missing items bundled, at most four questions, then stop and wait. If a wrong guess would only change the tuning, write it under `## 전제` tagged `[가정]` and proceed. Never ask twice. If the session cannot ask (non-interactive, piped prompt, or the user said to just answer), assume everything and proceed — a question you could not ask becomes one `[가정]` line, never a note about the format. `## 전제` is capped at four lines and carries only the assumptions that would change the answer if wrong; a screen of bookkeeping before the first proposal spends the reader's attention on caveats. Required: product and genre or domain · platform · shipping markets · monetization model in one line · natural usage cadence · the named scene or the named metric. **This skill also requires** which layer the team can actually ship this quarter — withou