Agent skill · Workflow & Productivity

pip-writer

Write a Performance Improvement Plan a manager can defend and an employee can actually act on — specific concerns, measurable goals, real support, and an honest timeline. Use when asked to write a PIP, put someone on a performance plan, document underperformance, or build a formal improvement plan. Produces the concern statement, the measurable goals with success criteria, the support plan, the check-in cadence, and the consequences — HR/legal-ready. Complements pip-responder (the employee's side).

mohitagw158561,255★ · 1 repos on radarProfile →
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill pip-writer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/pip-writer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# PIP Writer A Performance Improvement Plan fails when it's vague ("improve communication"), unfair (goals no one could hit), or a paper trail dressed as help. This writes the version that is genuinely fair *and* defensible: concrete concerns tied to examples, goals with measurable success criteria, the support the company will provide, and honest stakes — so the outcome is either a real turnaround or a decision no one can call arbitrary. > Not legal advice. Employment law varies by jurisdiction and contract — have HR/counsel review before delivery. ## What This Skill Produces - **The concern statement** — what's below bar, tied to specific, dated examples (not personality) - **The goals** — 2–4, each with a measurable success criterion and how it's evidenced - **The support plan** — what the manager/company will do (coaching, resources, time) - **The cadence** — check-in schedule and what each reviews - **The stakes & timeline** — the plan length, the review points, and the honest consequence of not meeting bar ## Required Inputs Ask for these if not provided: - **The role & bar** — what "meeting expectations" looks like for this level - **The specific gaps** — concrete instances,

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: A Fair, Defensible PIP
  4. Output Format
  5. Performance Improvement Plan — [name], [role]
  6. Areas of concern
  7. Improvement goals
  8. Support provided
  9. Check-ins
  10. Outcome
  11. Quality Checks
  12. Anti-Patterns
  13. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the pip-writer skill do?

Write a Performance Improvement Plan a manager can defend and an employee can actually act on — specific concerns, measurable goals, real support, and an honest timeline. Use when asked to write a PIP, put someone on a performance plan, document underperformance, or build a formal improvement plan. Produces the concern statement, the measurable goals with success criteria, the support plan, the check-in cadence, and the consequences — HR/legal-ready. Complements pip-responder (the employee's side).

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill pip-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going