performance-reviewer
Write performance reviews — self-assessments, manager evaluations, 360 feedback synthesis, and development plans.
Works with
--- name: performance-reviewer description: Write performance reviews — self-assessments, manager evaluations, 360 feedback synthesis, and development plans. license: MIT --- # Performance Reviewer ## Overview Write performance reviews — self-assessments, manager evaluations, 360 feedback synthesis, and development plans. ## When to Use This Skill Use **Performance Reviewer** when you need to: - Work with performance reviewer tasks in your project or workflow - Automate performance reviewer operations at scale - Generate production-quality performance reviewer output quickly ## Instructions When this skill is active, Claude will: 1. Understand the full context of your performance reviewer request 2. Apply best practices and conventions for Business & Productivity 3. Produce clean, well-structured, production-ready output 4. Explain key decisions and offer alternatives where relevant ## Examples ### Example 1 — Basic Usage **User:** Help me get started with performance reviewer. **Claude:** I'll walk you through the essential steps for performance reviewer in your context... ### Example 2 — Advanced Usage **User:** I need a production-ready performance reviewer setup with full error handling. **Claude:** Here's a complete, production-hardened performance reviewer implementation... ## Guidelines - Always validate inputs before processing - Follow the conventions of the target platform or language - Prefer explicit over implicit — clarity beats cleverness - Include comments for non-obvious logic - Suggest tests or validation steps where appropriate ## Dependencies Required: none ## Platforms Available on: claude.ai, api --- *Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.

