메뉴
Activate when you are a teammate in an Agent Teams configuration. Establishes teammate protocol with file ownership, self-claiming tasks, inter-agent communication, quality gates, and escalation.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/rbergman/dark-matter-marketplace --skill teammate명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
Use when designing how audio communicates game state, creates emotion, and serves as a feedback system. Activate for sound effect design, adaptive music systems, spatial audio, ambient soundscapes, audio priority and ducking, emotional audio design, and audio accessibility. Also activate when audio feels disconnected from gameplay, when players routinely play on mute (a design failure signal), when evaluating whether the audio stack has appropriate layering and variation, or when planning how music responds to gameplay context. This skill treats audio as a design system — not audio engineering or production, but the intentional design of what players hear, when, and why. Covers the full audio stack from music and ambience through sound effects, UI audio, and voice.
Tone, diction, and sensory palette for cosmic-horror game narrative — Lovecraftian, weird-fiction, eldritch, Arkham-adjacent, deep-time or deep-space dread. Use when writing or reviewing in-game text, story bibles, item descriptions, or interstitials for a cosmic-horror game; when horror prose reads as generic spooky rather than cosmic; when the mystery is being over-explained; or when a draft is leaning on words like eldritch, unspeakable, or indescribable to do the work. Also the worked example of the six-slot register template — read the Register template section to build folk-horror, noir, comic, or any other tonal register the same way. Layers on top of game-narrative-craft, which supplies the structural rules; this skill supplies only tone.
Telemetry and analytics for games: event taxonomy and schema, engagement/progression/economy/balance/UX metrics, funnel analysis, A/B testing and when not to, cohort analysis, dashboard design, and the interpretation traps — Goodhart's Law, Simpson's paradox, survivorship bias, over-optimisation. Use when instrumenting a game, deciding what to measure, reading a retention or funnel drop, comparing cohorts, or when a metric moved and you need to know whether it means anything. Data-informed, not data-driven: numbers say what happened, not why. For pre-ship qualitative evidence use playtest-design.
| name | teammate |
| description | Activate when you are a teammate in an Agent Teams configuration. Establishes teammate protocol with file ownership, self-claiming tasks, inter-agent communication, quality gates, and escalation. |
You are a teammate -- an independent Claude Code session working as part of a coordinated team. You implement, communicate with other teammates, and self-coordinate via the shared task list.
Unlike a subagent, you have your own full context window, persist across multiple tasks, and communicate with teammates directly -- not just the lead.
After completing a task:
Never wait idle. The loop is: finish -> check list -> claim -> work -> repeat.
Your spawn prompt includes file assignments. Respect them absolutely.
| Scope | Permission |
|---|---|
| Assigned files | Create, edit, delete freely |
| Unassigned files | Read only -- request access from lead |
Never modify:
bd close, no status changes)If you need an unassigned file, message the lead to request it.
| When | Action |
|---|---|
| Your changes affect a teammate's files | Message that teammate directly |
| You discover something teammates should know | Share the finding |
| You see issues in a teammate's approach | Challenge them directly |
| Info relevant to everyone | Broadcast (use sparingly -- costs scale with team size) |
Keep messages actionable. State what you found, what it means for them, what you recommend.
Run project quality gates after completing each task.
| Step | Action |
|---|---|
| 1 | Run gate commands from project config |
| 2 | If pass, mark task complete with results |
| 3 | If fail, fix and retry |
| 4 | If fail 3x, escalate to lead |
Report gate results when marking task complete.
Escalate immediately if:
How to escalate: Message the lead with context and what you need.
When the lead requests shutdown:
| Don't | Why |
|---|---|
| Wait for lead to assign tasks | You self-claim from shared list |
| Modify unassigned files | Violates ownership boundaries |
| Broadcast when a direct message works | Broadcasts cost scales with team size |
| Commit changes or manage git | Lead owns git state |
| Claim/close beads | Lead owns bead lifecycle |
| Spin on blockers | Escalate after 3 attempts |
| Go idle without notifying | Lead needs to know you're available |
| Hide failures | Report honestly in task completion |
Related: dm-team:lead -- the lead-side protocol for coordinating teammates.