people-report▌
anthropics/knowledge-work-plugins · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
/people-report
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate people analytics reports from your HR data. Analyze workforce data to surface trends, risks, and opportunities.
Usage
/people-report $ARGUMENTS
Report Types
Headcount: Current org snapshot — by team, location, level, tenure Attrition: Turnover analysis — voluntary/involuntary, by team, trends Diversity: Representation metrics — by level, team, pipeline Org Health: Span of control, management layers, team sizes, flight risk
Key Metrics
Retention
- Overall attrition rate (voluntary + involuntary)
- Regrettable attrition rate
- Average tenure
- Flight risk indicators
Diversity
- Representation by level, team, and function
- Pipeline diversity (hiring funnel by demographic)
- Promotion rates by group
- Pay equity analysis
Engagement
- Survey scores and trends
- eNPS (Employee Net Promoter Score)
- Participation rates
- Open-ended feedback themes
Productivity
- Revenue per employee
- Span of control efficiency
- Time to productivity for new hires
Approach
- Understand what question they're trying to answer
- Identify the right data (upload, paste, or pull from ~~HRIS)
- Analyze with appropriate statistical methods
- Present findings with context and caveats
- Recommend specific actions based on data
What I Need From You
Upload a CSV or describe your data. Helpful fields:
- Employee name/ID, department, team
- Title, level, location
- Start date, end date (if applicable)
- Manager, compensation (if relevant)
- Demographics (for diversity reports, if available)
Output
## People Report: [Type] — [Date]
### Executive Summary
[2-3 key takeaways]
### Key Metrics
| Metric | Value | Trend |
|--------|-------|-------|
| [Metric] | [Value] | [up/down/flat] |
### Detailed Analysis
[Charts, tables, and narrative for the specific report type]
### Recommendations
- [Data-driven recommendation]
- [Action item]
### Methodology
[How the numbers were calculated, any caveats]
If Connectors Available
If ~~HRIS is connected:
- Pull live employee data — headcount, tenure, department, level
- Generate reports without needing a CSV upload
If ~~chat is connected:
- Offer to share the report summary in a relevant channel
How to use people-report on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add people-report
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches people-report from GitHub repository anthropics/knowledge-work-plugins and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate people-report. Access the skill through slash commands (e.g., /people-report) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★39 reviews- ★★★★★Meera Bansal· Dec 28, 2024
We added people-report from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Shikha Mishra· Dec 24, 2024
Registry listing for people-report matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Diego Sethi· Dec 12, 2024
Solid pick for teams standardizing on skills: people-report is focused, and the summary matches what you get after install.
- ★★★★★Maya Sethi· Dec 4, 2024
people-report reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Min Mehta· Nov 23, 2024
people-report is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Hana White· Nov 19, 2024
Keeps context tight: people-report is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Diego Shah· Nov 15, 2024
people-report fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Meera Ghosh· Nov 3, 2024
people-report has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Nikhil Reddy· Oct 22, 2024
Keeps context tight: people-report is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Camila Agarwal· Oct 14, 2024
Useful defaults in people-report — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 39