Performance Review Writer
Use when drafting an evidence-based self-assessment, peer review, 360 feedback, or upward feedback in the user's voice.
Install
npx skills add sandbaseai/workbuddy-skill --skill performance-review-writergit clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/performance-review-writer ~/.claude/skills/performance-review-writerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 绩效反馈写作 把真实贡献和可观察行为整理成具体、诚实、建设性的绩效反馈。支持自评、同事评价、360 反馈和向上反馈;输出是供人审阅的草稿,不代替事实核验、管理判断或向公司系统提交。 ## 隐私与授权边界 - 开始前确认反馈类型、被评价对象/角色、评审周期、字数/表单限制、语气、读者、材料来源和授权范围;没有这些信息时先列最小问题,不猜测身份或周期。 - 只使用用户明确授权的邮件、聊天、会议记录、项目文档、指标或用户提供的要点;默认不要检索整个邮箱、私聊、私人日历或与评审无关的线程。 - 处理同事、客户和下属信息时坚持最小化:只保留与工作行为和结果有关的内容,删除私人细节、健康/家庭信息、敏感身份、无关参与者和完整原文。 - 不编造项目、数字、赞扬、因果、评价或引用;证据不足写 `[NEEDS DETAIL]` 或 `unknown`。推断必须标明为推断,并允许用户删改。 - 不发送邮件、写入 HR 系统、提交评价、通知被评价者或改变任何记录;只在已授权本地目录保存草稿,提交动作永远由用户完成。 ## 反馈类型 | 类型 | 关注对象 | 推荐语气与证据 | |---|---|---| | Self-assessment | 自己 | 自信、具体、成长导向;贡献与影响 | | Peer review | 同事 | 平衡、尊重、可观察行为;协作与结果 | | 360 feedback | 多方关系 | 分离事实与观点;说明观察范围和限制 | | Upward feedback | 经理/负责人 | 外显行为、影响和可行动请求;不评价人格 | 先确认表单真正需要的类型;同一材料不能未经重写就复制到不同类型。匿名反馈要避免能反推出身份的独特细节,并说明匿名性由系统而非 WorkBuddy 保证。 ## 工作流 ### 1. 收集上下文 建立范围卡:周期、角色、目标、项目、责任、读者、提交格式、字数和排除项。若授权的企业搜索连接器可用,只检索时间、项目和参与者范围内的相关证据,先输出证据摘要和来源类别,不直接复制原文。若连接器不可用,请用户提供 3–5 个要点、指标或链接;不要为了补全而访问未授权资料。 ### 2. 建立证据账本 每条候选贡献记录 Situation、Task、Action、Result(STAR)、来源、日期、作者/角色(能匿名则匿名)、置信度和缺口。区分: - `observed`:材料直接支持的事实; - `derived`:由多个事实计算或归纳的结果,写出推导; - `reported`:他人反馈或用户回忆,标注来源类别; - `unknown`:无法验证的数字、因果或范围。 只使用与周期相关且可公开给评审读者的证据;不要把一次赞扬推广成稳定特质,不要把相关性写成因果,不要将活动数量当成果质量。 ### 3. 起草与校准 每个成就尽量使用:背景/挑战 → 责任 → 具体行动 → 影响/结果 → 学习/下一步。写清项目、行为、受影响用户/团队和可验证结果;没有数字时使用可观察变化,不用伪精确百分比。避免“team player”“above and beyond”“hard worker”等空泛词,改为行为和结果。 自评可包含总结、3–5 项关键成就、协作与影响、成长、发展方向和下一周期目标;同事评价聚焦优势、具体例子、成长建议和合作体验;向上反馈聚焦有效做法、行为影响和一个清晰请求。发展建议针对行为和环境,不针对人格、动机、年龄、外貌或其他受保护特征。 ### 4. 审阅与交付
Details
- Skill name
performance-review-writer- Repository
- sandbaseai/workbuddy-skill
- Path
skills/performance-review-writer/SKILL.md- License
- MIT
- Repo updated
- 8 September 2026
FAQ
What does the Performance Review Writer skill do?
Use when drafting an evidence-based self-assessment, peer review, 360 feedback, or upward feedback in the user's voice.
How do I install the Performance Review Writer skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill performance-review-writer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Performance Review Writer popular?
It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.
Related skills
Access Control Security Best Practices
9sandbaseai/workbuddy-skill
Design, review, implement, and verify least-privilege access controls across users, services, tenants, resources, and administrative workflows.
Accessibility Review
9sandbaseai/workbuddy-skill
Use when reviewing a web interface or interaction for semantic, keyboard, focus, screen-reader, ARIA, and contrast accessibility risks.
Acquire Codebase Knowledge
9sandbaseai/workbuddy-skill
Use when the user asks to map, document, or onboard into an existing codebase and needs evidence-backed architecture, structure, conventions, integrations, testing, and concerns documentation.
Postmortem Writing
9sandbaseai/workbuddy-skill
Use after an incident, near miss, or reliability event to produce a blameless, evidence-grounded postmortem with a timeline, contributing conditions, actions, owners, and follow-up verification.
Microsoft Docs
9sandbaseai/workbuddy-skill
Use when researching Microsoft technologies with official documentation search, code samples, and page retrieval, keeping citations, version context, and uncertainty explicit.
Readme Sync
9sandbaseai/workbuddy-skill
Use after changes to features, commands, configuration, dependencies, APIs, project structure, or deployment workflows to keep README documentation aligned with the current repository and remove unsupported claims.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.