engagement-analyzer
Analyze employee engagement survey data to identify trends, prioritize actions, and design targeted interventions
What this skill does
# 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:**
1. Priority area
2. Root cause hypothesis
3. Proposed intervention
4. Success metrics
5. 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 support
- `onboarding-guide` - Initial engagement
- `churn-prediction` - Turnover risk
## Skill Metadata
- **Domain**: HR Operations
- **Complexity**: Intermediate-Advanced
- **Mode**: centaur
- **Time to Value**: 2-4 hours per anaRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.