performance-review
Structure a performance review with self-assessment, manager template, and calibration prep. Use when review season kicks off and you need a self-assessment template, writing a manager review for a direct report, prepping rating distributions and promotion cases for calibration, or turning vague feedback into specific behavioral examples.
What this skill does
# /performance-review > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Generate performance review templates and help structure feedback. ## Usage ``` /performance-review $ARGUMENTS ``` ## Modes ``` /performance-review self-assessment # Generate self-assessment template /performance-review manager [employee] # Manager review template for a specific person /performance-review calibration # Calibration prep document ``` If no mode is specified, ask what type of review they need. ## Output — Self-Assessment Template ```markdown ## Self-Assessment: [Review Period] ### Key Accomplishments [List your top 3-5 accomplishments this period. For each, describe the situation, your contribution, and the impact.] 1. **[Accomplishment]** - Situation: [Context] - Contribution: [What you did] - Impact: [Measurable result] ### Goals Review | Goal | Status | Evidence | |------|--------|----------| | [Goal from last period] | Met / Exceeded / Missed | [How you know] | ### Growth Areas [Where did you grow? New skills, expanded scope, leadership moments.] ### Challenges [What was hard? What would you do differently?] ### Goals for Next Period 1. [Goal — specific and measurable] 2. [Goal] 3. [Goal] ### Feedback for Manager [How can your manager better support you?] ``` ## Output — Manager Review ```markdown ## Performance Review: [Employee Name] **Period:** [Date range] | **Manager:** [Your name] ### Overall Rating: [Exceeds / Meets / Below Expectations] ### Performance Summary [2-3 sentence overall assessment] ### Key Strengths - [Strength with specific example] - [Strength with specific example] ### Areas for Development - [Area with specific, actionable guidance] - [Area with specific, actionable guidance] ### Goal Achievement | Goal | Rating | Comments | |------|--------|----------| | [Goal] | [Rating] | [Specific observations] | ### Impact and Contributions [Describe their biggest contributions and impact on the team/org] ### Development Plan | Skill | Current | Target | Actions | |-------|---------|--------|---------| | [Skill] | [Level] | [Level] | [How to get there] | ### Compensation Recommendation [Promotion / Equity refresh / Adjustment / No change — with justification] ``` ## Output — Calibration ```markdown ## Calibration Prep: [Review Cycle] **Manager:** [Your name] | **Team:** [Team] | **Period:** [Date range] ### Team Overview | Employee | Role | Level | Tenure | Proposed Rating | Notes | |----------|------|-------|--------|-----------------|-------| | [Name] | [Role] | [Level] | [X years] | [Rating] | [Key context] | ### Rating Distribution | Rating | Count | % of Team | Company Target | |--------|-------|-----------|----------------| | Exceeds Expectations | [X] | [X]% | ~15-20% | | Meets Expectations | [X] | [X]% | ~60-70% | | Below Expectations | [X] | [X]% | ~10-15% | ### Calibration Discussion Points 1. **[Employee]** — [Why this rating may need discussion, e.g., borderline, first review at level, recent role change] 2. **[Employee]** — [Discussion point] ### Promotion Candidates | Employee | Current Level | Proposed Level | Justification | |----------|-------------|----------------|---------------| | [Name] | [Current] | [Proposed] | [Evidence of next-level performance] | ### Compensation Actions | Employee | Action | Justification | |----------|--------|---------------| | [Name] | [Promotion / Equity refresh / Market adjustment / Retention] | [Why] | ### Manager Notes [Context the calibration group should know — team changes, org shifts, project impacts] ``` ## If Connectors Available If **~~HRIS** is connected: - Pull prior review history and goal tracking data - Pre-populate employee details and current role information If **~~project tracker** is connected: - Pull completed work and contributions for the review period - Reference specific tickets and project milestones as evidence ## Tips 1. **Be specific** — "Great job" isn't feedback. "You reduced deploy time 40% by implementing the new CI pipeline" is. 2. **Balance positive and constructive** — Both are essential. Neither should be a surprise. 3. **Focus on behaviors, not personality** — "Your documentation has been incomplete" vs. "You're careless." 4. **Make development actionable** — "Improve communication" is vague. "Present at the next team all-hands" is actionable.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.