plugins/pm-career/skills/self-review/SKILL.md
Write a performance self-review that's specific, evidenced, and balanced. Use when asked to write a self-review, self-assessment, or self-evaluation for a performance cycle. Produces a complete self-review — accomplishments mapped to impact and competencies, growth areas owned honestly, and a forward-looking development plan, in the voice of the person being reviewed.
npx skillsauth add mohitagw15856/pm-claude-skills self-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A self-review is your one chance to frame your own year before someone else does. Done badly it's a
vague list of activities; done well it's an evidenced narrative that maps your work to the competencies
you're measured on, owns growth honestly, and sets up the next level. This skill writes that — pulling
straight from a brag-doc if you have one.
Ask for these only if they aren't already provided:
1. Summary — 3–4 sentences: the headline of your period and the through-line. Lead with impact.
2. Key accomplishments — your top 3–6, each as outcome → your contribution → evidence → which competency it demonstrates. Quantify; tie to team/company goals.
3. Strengths — the 2–3 competencies you most demonstrated, with the proof.
4. Growth areas — 1–3, owned plainly: what was hard, what you learned, what you're changing. This section builds credibility when it's specific and non-defensive (not "I work too hard").
5. Goals & development plan — what you'll focus on next period and the support you need.
6. Rating rationale (if self-rating) — the rating you'd give and the evidence for it, calibrated to the framework — not inflated, not falsely modest.
Competency-based performance-review practice — evidence-mapped accomplishments and calibrated self-assessment.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.