engagement-analyzer
정보
이 스킬은 직원 참여도 설문 데이터를 분석하여 주요 동향을 파악하고 실행 가능한 통찰력을 우선순위화합니다. 개발자들이 Gallup Q12와 같은 검증된 프레임워크를 기반으로 원시 설문 결과를 표적화된 개입 전략으로 전환할 수 있도록 지원합니다. 설문 데이터 세트에서 참여도 동인을 신속하게 찾아내고 데이터 기반 개선 계획을 수립하는 데 활용하세요.
빠른 설치
Claude Code
추천npx skills add guia-matthieu/clawfu-skills -a claude-code/plugin add https://github.com/guia-matthieu/clawfu-skillsgit clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/engagement-analyzerClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Engagement Analyzer
Transform engagement survey data into actionable insights with trend analysis, priority identification, and targeted intervention design.
When to Use This Skill
- Analyzing survey results
- Identifying engagement drivers
- Prioritizing action areas
- Designing interventions
- Tracking improvement
Methodology Foundation
Based on Gallup Q12 framework and Qualtrics engagement research, combining:
- Driver analysis
- Benchmarking
- Action prioritization
- Intervention design
What Claude Does vs What You Decide
| Claude Does | You Decide |
|---|---|
| Analyzes survey data | Survey questions |
| Identifies patterns | Data collection |
| Prioritizes actions | Resource allocation |
| Suggests interventions | Implementation |
| Creates action plans | Executive priorities |
Instructions
Step 1: Understand Engagement Model
Key Engagement Dimensions:
| Dimension | What It Measures | Example Questions |
|---|---|---|
| Purpose | Connection to mission | "My work has meaning" |
| Development | Growth opportunity | "I learn and grow here" |
| Manager | Leadership quality | "My manager supports me" |
| Team | Collaboration | "My team works well together" |
| Wellbeing | Work-life balance | "I can manage my workload" |
| Recognition | Appreciation | "I feel valued for my contributions" |
Step 2: Analyze Results
Analysis Framework:
| Metric | Calculation | Interpretation |
|---|---|---|
| Overall Score | Average of all items | Health indicator |
| Favorability | % Agree + Strongly Agree | Positive sentiment |
| eNPS | Promoters - Detractors | Loyalty indicator |
| Participation | Responses / Invited | Data reliability |
Comparison Points:
- Previous survey (trend)
- Company benchmark
- Industry benchmark
- Team vs. company
Step 3: Identify Priorities
Priority Matrix:
| Score | Impact | Priority |
|---|---|---|
| Low | High | P1 - Critical |
| Low | Medium | P2 - Important |
| Low | Low | P3 - Monitor |
| High | Any | Maintain |
Step 4: Design Interventions
Intervention Types:
| Level | Examples | Timeline |
|---|---|---|
| Quick Wins | Recognition, communication | 0-30 days |
| Process Changes | Meeting structure, feedback | 30-90 days |
| Structural Changes | Role design, team structure | 90+ days |
| Culture Shifts | Values, behaviors | 6+ months |
Step 5: Create Action Plan
Plan Components:
- Priority area
- Root cause hypothesis
- Proposed intervention
- Success metrics
- Owner and timeline
Examples
Example 1: Full Engagement Analysis
Input:
Analyze these engagement survey results:
Company Overall: 72 (was 68)
Participation: 85%
By Dimension (favorability %):
- Purpose: 82%
- Development: 58%
- Manager: 71%
- Team: 76%
- Wellbeing: 54%
- Recognition: 65%
Engineering Dept: 64 overall
- Development: 45%
- Wellbeing: 42%
Sales Dept: 78 overall
- Recognition: 52%
Output:
## Employee Engagement Analysis
### Executive Summary
**Overall Health:** Improving (+4 points to 72)
**Key Wins:** Purpose (82%), Team (76%)
**Critical Areas:** Wellbeing (54%), Development (58%)
**Hot Spots:** Engineering (64 overall), Sales Recognition (52%)
---
### Overall Results
| Metric | Score | vs. Last | vs. Benchmark |
|--------|-------|----------|---------------|
| Overall Score | 72 | +4 | +2 |
| Participation | 85% | +3% | +10% |
| eNPS | +18 | +6 | +8 |
**Interpretation:** Solid improvement across the board. High participation
indicates employees feel their voice matters.
---
### Dimension Analysis
| Dimension | Score | Trend | Priority |
|-----------|-------|-------|----------|
| Purpose | 82% | → | Maintain |
| Team | 76% | ↑ | Maintain |
| Manager | 71% | ↑ | Improve |
| Recognition | 65% | → | Improve |
| Development | 58% | ↓ | Critical |
| Wellbeing | 54% | ↓ | Critical |
---
### Priority Matrix
HIGH IMPACT
│
┌────────────────────┼────────────────────┐
│ P1: CRITICAL │ MAINTAIN │
│ • Wellbeing │ • Purpose │
│ • Development │ • Team │
LOW ├────────────────────┼────────────────────┤ HIGH SCORE│ P2: IMPORTANT │ LEVERAGE │ │ • Recognition │ │ │ • Manager │ │ └────────────────────┴────────────────────┘ LOW IMPACT
---
### Department Deep Dive
#### Engineering (64 Overall) - NEEDS ATTENTION
| Dimension | Engineering | Company | Gap |
|-----------|-------------|---------|-----|
| Development | 45% | 58% | -13 |
| Wellbeing | 42% | 54% | -12 |
**Root Cause Hypotheses:**
1. Technical debt creating burnout
2. Limited career progression paths
3. On-call burden distributed unevenly
**Recommended Actions:**
| Action | Owner | Timeline |
|--------|-------|----------|
| Engineering career ladder review | VP Eng + HR | 90 days |
| On-call rotation audit | Eng Managers | 30 days |
| 20% learning time policy | VP Eng | 60 days |
---
### Company-Wide Action Plan
#### P1: Wellbeing Initiative (54%)
**Target:** Increase to 65% by next survey
**Actions:**
| Action | Owner | Timeline |
|--------|-------|----------|
| "No Meeting Fridays" pilot | Leadership | 30 days |
| Workload survey by department | HRBP | 30 days |
| Manager training: sustainable teams | L&D | 90 days |
---
#### P1: Development Initiative (58%)
**Target:** Increase to 70% by next survey
**Actions:**
| Action | Owner | Timeline |
|--------|-------|----------|
| Learning stipend communication | HR | 30 days |
| Career pathing by function | HR + Leaders | 90 days |
| Mentorship program launch | L&D | 90 days |
---
### Success Metrics
| Area | Current | 6-Month Target | Owner |
|------|---------|----------------|-------|
| Overall Score | 72 | 76 | CHRO |
| Wellbeing | 54% | 65% | HR |
| Development | 58% | 70% | L&D |
| Engineering Overall | 64 | 72 | VP Eng |
Example 2: Quick Pulse Analysis
Input:
Analyze this pulse survey (3 questions):
1. "I would recommend this company" - 62% favorable (down 8%)
2. "I have what I need to do my job" - 71% favorable (up 3%)
3. "I feel valued" - 48% favorable (down 12%)
Output:
## Pulse Survey Quick Analysis
### Summary
| Metric | Current | Change | Status |
|--------|---------|--------|--------|
| eNPS Indicator | 62% | ↓ 8% | WARNING |
| Enablement | 71% | ↑ 3% | GOOD |
| Recognition | 48% | ↓ 12% | CRITICAL |
---
### Key Finding
**Recognition is in crisis** - 12-point drop is a red flag.
This is likely driving the eNPS decline.
---
### Immediate Actions
| Priority | Action | Owner | Timeline |
|----------|--------|-------|----------|
| 1 | Leadership acknowledgment | CEO | This week |
| 2 | Manager recognition training | HR | 2 weeks |
| 3 | Focus groups on "valued" | HRBP | 2 weeks |
Skill Boundaries
What This Skill Does Well
- Analyzing survey patterns
- Prioritizing action areas
- Designing interventions
- Creating action plans
What This Skill Cannot Do
- Access actual survey data
- Know company-specific context
- Replace qualitative research
- Guarantee improvement
Iteration Guide
Follow-up Prompts:
- "Create focus group questions for [area]"
- "Design intervention for [specific issue]"
- "How do we communicate results to [audience]?"
- "What metrics should we track for [initiative]?"
References
- Gallup Q12 Engagement Framework
- Qualtrics Employee Experience
- Culture Amp Engagement Drivers
- Glint People Science
Related Skills
employee-support- Ongoing supportonboarding-guide- Initial engagementchurn-prediction- Turnover risk
Skill Metadata
- Domain: HR Operations
- Complexity: Intermediate-Advanced
- Mode: centaur
- Time to Value: 2-4 hours per analysis
- Prerequisites: Survey data, company context
GitHub 저장소
연관 스킬
executing-plans
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
