원클릭으로
team-analysis
Use this skill when analyzing team dynamics, workload distribution, hidden contributions, or individual performance context.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use this skill when analyzing team dynamics, workload distribution, hidden contributions, or individual performance context.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use this skill when investigating blockers, stalled work, or anything preventing progress.
Use this skill when the user asks about deepagents harness capabilities, tool names, task delegation, filesystem access, or sandbox execution. It provides a concise operational cheat sheet.
Use this skill for multi-track tasks that benefit from delegation, parallel research, or structured planning. It guides the main agent to use the task tool, subagents, and write_todos for coordination.
Use this skill for requests related to Linear issues, projects, sprints, and team workload. This skill provides guidance on how to effectively query and interact with Linear data.
Use this skill when generating project updates, status reports, or stakeholder communications.
Use this skill for tasks that require running commands or scripts in the sandbox. It provides a plan-first workflow for using run_sandbox_workflow, dependency setup, verification, and iterative loops.
| name | team-analysis |
| description | Use this skill when analyzing team dynamics, workload distribution, hidden contributions, or individual performance context. |
This skill helps surface hidden contributions and provides context for team member performance.
Traditional metrics miss the real story. Some people close 10 small tickets; others spend a week on complex architecture. Both are valuable.
When asked about someone's output, search for the fuller picture:
Use search_memories with query for the person's name plus terms like:
Look for force-multiplier work: reviews, mentoring, unblocking others.
Structure your response:
[Name] this week:
**Visible work:**
- 2 tickets completed
**Hidden impact:**
- 4 code reviews unblocking others
- Architecture discussion shaping API design
- Helped debug auth issue (saved ~day)
**Assessment:**
Force-multiplier work that doesn't show in ticket counts.