fix(plugins): sync all 171 plugin SKILL.md files with fixed skills/ versions

Propagates Anti-Patterns sections, description rewrites, Required Inputs
additions, and Quality Checks format fixes from skills/ to matching plugin
SKILL.md copies.

https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
This commit is contained in:
Mohit
2026-06-08 13:06:21 +00:00
parent fb85a1cb55
commit affae033fe
171 changed files with 1428 additions and 56 deletions
@@ -7,6 +7,18 @@ description: "Design an employee engagement survey and analyse results. Use when
Designs complete employee engagement surveys and provides a framework for analysing and acting on results.
## Required Inputs
Ask the user for these if not provided:
- **Mode** — designing a new survey or analysing existing results
- **Survey type** (annual / quarterly pulse / post-onboarding / exit / specific topic)
- **Company name** (for personalisation of question text)
- **Company size and stage** (startup / scaleup / enterprise — affects question relevance)
- **Key areas of concern** (optional — e.g. "we have had high attrition on the engineering team")
- **Anonymity approach** — fully anonymous, team-level reporting only, or individual responses visible to HR
- **Length target** (short: 510 questions / standard: 1525 / comprehensive: 30+)
- **For analysis mode:** survey results data (paste as table, CSV, or summary statistics)
## Mode Detection
- User provides survey results -> Analysis mode
- User wants to create a survey -> Design mode
@@ -88,6 +100,14 @@ eNPS: Below 0 = Concerning / 0-30 = Good / 30-70 = Great / 70+ = Excellent
- [ ] Analysis includes a specific action planning template (not just observations)
- [ ] Results communication template commits to sharing back with employees by a specific date
## Anti-Patterns
- [ ] Do not launch a survey without committing to a communication-back date — surveys with no follow-through reduce trust and depress future response rates
- [ ] Do not use only Likert scale questions — open-text responses surface specific themes that quantitative scores cannot, and are essential for action planning
- [ ] Do not design a comprehensive 30+ question survey as a pulse — pulse surveys that take more than 5 minutes see sharply lower completion rates
- [ ] Do not present analysis without an action planning template — raw scores without committed actions are the most common reason engagement survey data is ignored
- [ ] Do not segment results below teams of 5 when anonymity is promised — small-group breakdowns allow individual identification and destroy psychological safety
## Example Trigger Phrases
- "Create an employee engagement survey for our team"
- "Design a pulse survey for [topic]"