65 team performance review global skill

Use when a leader evaluates a marketing TEAM MEMBER using data — a KPI scorecard by role, strengths with real examples, areas to improve stated as observable behavior, a 30 and 90 day development plan, and a 1-5 rating rubric.

by minhnv0807·MIT license·★ 599 Stars on the repo·GitHub ↗

Use now

Files of 65 team performance review global

minhnv0807/master1 file shown
SKILL.md
Show the full text155 lines

Team Performance Review (Global)

A review is not a grade — it exists so the person knows what to do to get better. Feedback without data is opinion; feedback with data is coaching. There should be no surprises in a review: feedback is given continuously through the period, and the review only summarizes it.

Information gathering

Read the brief history (64-team-brief-global), last period's output, and the reports (07-marketing-report-global) if available. If missing, ask up to 4 questions:

  1. Who is being reviewed, in what role, for what period? Content writer / designer / media buyer / channel owner; monthly or quarterly.
  2. What KPIs were set at the start of the period? If none were set, this review can only be qualitative — say so explicitly in the document.
  3. Concrete output data: pieces published, assets delivered, CPA/ROAS on campaigns they own, on-time rate, revisions per task.
  4. Specific observations from the period: 2-3 real situations (positive and negative) with dates.

Principles

  1. No surprises. Negative feedback is given when it happens, not saved for review day.
  2. Every statement needs evidence. "Hard-working" is not an assessment; "on time on 9 of 10 tasks, proposed two new content angles unprompted" is.
  3. Assess behavior, not character. Write "submitted late 3 times without notice", not "irresponsible".
  4. Rate consistently. Apply the same standard across the team; do not let personal rapport shift the scale.
  5. A review must produce a development plan. Without one it is just an unusable scorecard.
  6. The document is confidential. Leader and reviewee only.

Documentation caution

In many jurisdictions, written performance documentation carries employment-law weight and can be produced as evidence in a dispute. Write it accordingly:

  • Record observable behavior and measurable outcomes with dates — what was delivered, when, against what agreed standard.
  • Avoid subjective characterizations, comparisons to other individuals, and anything touching protected characteristics (age, gender, race, religion, disability, pregnancy, national origin, or similar).
  • Do not put speculation about a person's attitude, motives, personal circumstances, or health in the document.
  • Keep this review separate from any discussion of discipline, termination, or compensation changes. This skill does not give legal or HR advice. Anything termination-adjacent, any performance improvement plan with employment consequences, and any cross-border reporting line should go to HR or employment counsel before it is written or delivered.

KPIs by role

Role Quantitative KPIs Qualitative KPIs
Content writer Pieces per month, on-time rate, revisions per piece, engagement rate on their work On-brand voice, sharpness of the angle, proactively proposing angles
Designer Assets per month, on-time rate, share approved on the first pass, design review score Understands briefs, follows the brand guideline, handles asset gaps
Media buyer CPA vs target, ROAS, share of campaigns hitting KPI, optimization frequency Tracking discipline, quality of the test log, flags risks early
Channel owner Response SLA, share of channels set up to checklist, open and click rates Incident handling, cross-functional coordination

If no KPI was set for the role at the start of the period, the first action after the review is to set KPIs for the next period. Do not measure someone against a standard they never saw.

Output structure

# Performance Review — [Name] — [Period]

Role: [role] · Reviewer: [leader] · Date: [date]

## I. KPI scorecard
| KPI set at period start | Target | Actual | % achieved | Note |
|-------------------------|--------|--------|------------|------|
| [Role KPI 1] | | | | |
| [Role KPI 2] | | | | |
| On-time delivery rate | | | | |
| Revisions per task | | | | |

KPI summary: Met / Near / Not met — with the specific numbers.

## II. Strengths this period
| Strength | Specific example (date + situation) | Impact on the team or KPI |
|----------|-------------------------------------|---------------------------|

## III. Areas to improve
| Item | Observed behavior | Actual impact | Specific expectation |
|------|-------------------|---------------|----------------------|

## IV. Development plan
30-day goals:
- [ ] [Specific, measurable skill or behavior]

90-day goals:
- [ ] [...]

Support from the leader: [training, materials, check-in frequency]

## V. Feedback from the team member
- What do they think they contributed this period?
- What support do they need from the leader?
- What is blocking them that the leader does not know about?
- Which direction do they want to grow?

## VI. Overall rating
| Criterion | Score 1-5 | Comment |
|-----------|-----------|---------|
| Output quality | | |
| On-time delivery | | |
| Initiative | | |
| Communication and collaboration | | |
| Learning and improvement speed | | |
| **Overall** | | |

Scale: 1 = needs significant improvement · 3 = meets expectations · 5 = exceeds expectations.

## VII. Next steps
- [ ] Send the document to the reviewee within 24 hours of the 1:1
- [ ] Set a 30-day follow-up reminder
- [ ] Any compensation change: route through HR before it is stated in writing

1:1 session format (60 minutes)

Duration Content
5 min Ask for their self-assessment first
20 min Walk the KPIs and data together
20 min Strengths and areas to improve, listen to their response
10 min Development plan — discuss until they agree, do not impose
5 min Their feedback for the leader

The leader prepares the document before the session and does not write it live during the meeting. For distributed teams, hold the 1:1 on video rather than in writing — written-only performance feedback reads harsher than intended and removes the chance to respond.

  • 64-team-brief-global: source of on-time rate and revision counts.
  • 62-marketing-review-global and 47-design-review-global: approval outcomes serve as quantitative evidence.
  • 63-campaign-retrospective-global: the retro covers the system, this review covers the individual — never merge the two documents.
  • 07-marketing-report-global: results for the channels or campaigns they own.

Quality checklist

  • Every statement has a real example with a date or a number
  • No negative feedback appears here for the first time
  • Assessments describe observable behavior and measurable outcomes, not character
  • No subjective characterizations, peer comparisons, or references to protected characteristics
  • Development plan has 30-day and 90-day goals that are measurable
  • Includes support from the leader, not only demands on the employee
  • Includes a section capturing the team member's feedback upward
  • Ratings use the same scale applied to everyone in the same role
  • Anything termination-adjacent or compensation-related routed to HR or counsel before it is written
1---
2name: 65-team-performance-review-global
3description: "Use when a leader evaluates a marketing TEAM MEMBER using data — a KPI scorecard by role, strengths with real examples, areas to improve stated as observable behavior, a 30 and 90 day development plan, and a 1-5 rating rubric. Trigger on 'performance review for my marketer', 'evaluate a team member', 'monthly 1:1 review', 'feedback for my content writer', 'development plan for an employee', 'is this person underperforming'. Also use when the user is unhappy with someone and cannot articulate why. Not for — evaluating a campaign rather than a person, see `63-campaign-retrospective-global`; reviewing one piece of output, see `62-marketing-review-global`; scoring an external vendor, see `67-agency-vendor-brief-global`."
4metadata:
5 version: 1.0.1
6 category: operations
7license: MIT
8triggers:
9 - "performance review"
10 - "evaluate a team member"
11 - "review my marketing team"
12 - "monthly 1:1 review"
13 - "feedback for a team member"
14 - "development plan for an employee"
15 - "KPI scorecard by role"
16output: "File .md — full review: KPI scorecard, strengths, areas to improve, 30/90-day development plan, rating rubric, next steps"
17related:
18 - 64-team-brief-global
19 - 63-campaign-retrospective-global
20 - 07-marketing-report-global
21 - 62-marketing-review-global
22 - 47-design-review-global
23---
24 
25# Team Performance Review (Global)
26 
27> A review is not a grade — it exists so the person knows what to do to get better. Feedback without data is opinion; feedback with data is coaching. There should be no surprises in a review: feedback is given continuously through the period, and the review only summarizes it.
28 
29## Information gathering
30 
31Read the brief history (`64-team-brief-global`), last period's output, and the reports (`07-marketing-report-global`) if available. If missing, ask up to 4 questions:
32 
331. **Who is being reviewed, in what role, for what period?** Content writer / designer / media buyer / channel owner; monthly or quarterly.
342. **What KPIs were set at the start of the period?** If none were set, this review can only be qualitative — say so explicitly in the document.
353. **Concrete output data:** pieces published, assets delivered, CPA/ROAS on campaigns they own, on-time rate, revisions per task.
364. **Specific observations from the period:** 2-3 real situations (positive and negative) with dates.
37 
38## Principles
39 
401. **No surprises.** Negative feedback is given when it happens, not saved for review day.
412. **Every statement needs evidence.** "Hard-working" is not an assessment; "on time on 9 of 10 tasks, proposed two new content angles unprompted" is.
423. **Assess behavior, not character.** Write "submitted late 3 times without notice", not "irresponsible".
434. **Rate consistently.** Apply the same standard across the team; do not let personal rapport shift the scale.
445. **A review must produce a development plan.** Without one it is just an unusable scorecard.
456. **The document is confidential.** Leader and reviewee only.
46 
47## Documentation caution
48 
49In many jurisdictions, written performance documentation carries employment-law weight and can be produced as evidence in a dispute. Write it accordingly:
50 
51- Record **observable behavior and measurable outcomes** with dates — what was delivered, when, against what agreed standard.
52- Avoid subjective characterizations, comparisons to other individuals, and anything touching protected characteristics (age, gender, race, religion, disability, pregnancy, national origin, or similar).
53- Do not put speculation about a person's attitude, motives, personal circumstances, or health in the document.
54- Keep this review separate from any discussion of discipline, termination, or compensation changes. **This skill does not give legal or HR advice.** Anything termination-adjacent, any performance improvement plan with employment consequences, and any cross-border reporting line should go to HR or employment counsel before it is written or delivered.
55 
56## KPIs by role
57 
58| Role | Quantitative KPIs | Qualitative KPIs |
59|------|-------------------|------------------|
60| Content writer | Pieces per month, on-time rate, revisions per piece, engagement rate on their work | On-brand voice, sharpness of the angle, proactively proposing angles |
61| Designer | Assets per month, on-time rate, share approved on the first pass, design review score | Understands briefs, follows the brand guideline, handles asset gaps |
62| Media buyer | CPA vs target, ROAS, share of campaigns hitting KPI, optimization frequency | Tracking discipline, quality of the test log, flags risks early |
63| Channel owner | Response SLA, share of channels set up to checklist, open and click rates | Incident handling, cross-functional coordination |
64 
65If no KPI was set for the role at the start of the period, the first action after the review is to set KPIs for the next period. Do not measure someone against a standard they never saw.
66 
67## Output structure
68 
69```markdown
70# Performance Review — [Name] — [Period]
71 
72Role: [role] · Reviewer: [leader] · Date: [date]
73 
74## I. KPI scorecard
75| KPI set at period start | Target | Actual | % achieved | Note |
76|-------------------------|--------|--------|------------|------|
77| [Role KPI 1] | | | | |
78| [Role KPI 2] | | | | |
79| On-time delivery rate | | | | |
80| Revisions per task | | | | |
81 
82KPI summary: Met / Near / Not met — with the specific numbers.
83 
84## II. Strengths this period
85| Strength | Specific example (date + situation) | Impact on the team or KPI |
86|----------|-------------------------------------|---------------------------|
87 
88## III. Areas to improve
89| Item | Observed behavior | Actual impact | Specific expectation |
90|------|-------------------|---------------|----------------------|
91 
92## IV. Development plan
9330-day goals:
94- [ ] [Specific, measurable skill or behavior]
95 
9690-day goals:
97- [ ] [...]
98 
99Support from the leader: [training, materials, check-in frequency]
100 
101## V. Feedback from the team member
102- What do they think they contributed this period?
103- What support do they need from the leader?
104- What is blocking them that the leader does not know about?
105- Which direction do they want to grow?
106 
107## VI. Overall rating
108| Criterion | Score 1-5 | Comment |
109|-----------|-----------|---------|
110| Output quality | | |
111| On-time delivery | | |
112| Initiative | | |
113| Communication and collaboration | | |
114| Learning and improvement speed | | |
115| **Overall** | | |
116 
117Scale: 1 = needs significant improvement · 3 = meets expectations · 5 = exceeds expectations.
118 
119## VII. Next steps
120- [ ] Send the document to the reviewee within 24 hours of the 1:1
121- [ ] Set a 30-day follow-up reminder
122- [ ] Any compensation change: route through HR before it is stated in writing
123```
124 
125## 1:1 session format (60 minutes)
126 
127| Duration | Content |
128|----------|---------|
129| 5 min | Ask for their self-assessment first |
130| 20 min | Walk the KPIs and data together |
131| 20 min | Strengths and areas to improve, listen to their response |
132| 10 min | Development plan — discuss until they agree, do not impose |
133| 5 min | Their feedback for the leader |
134 
135The leader prepares the document before the session and does not write it live during the meeting. For distributed teams, hold the 1:1 on video rather than in writing — written-only performance feedback reads harsher than intended and removes the chance to respond.
136 
137## Related skills
138 
139- `64-team-brief-global`: source of on-time rate and revision counts.
140- `62-marketing-review-global` and `47-design-review-global`: approval outcomes serve as quantitative evidence.
141- `63-campaign-retrospective-global`: the retro covers the system, this review covers the individual — never merge the two documents.
142- `07-marketing-report-global`: results for the channels or campaigns they own.
143 
144## Quality checklist
145 
146- [ ] Every statement has a real example with a date or a number
147- [ ] No negative feedback appears here for the first time
148- [ ] Assessments describe observable behavior and measurable outcomes, not character
149- [ ] No subjective characterizations, peer comparisons, or references to protected characteristics
150- [ ] Development plan has 30-day and 90-day goals that are measurable
151- [ ] Includes support from the leader, not only demands on the employee
152- [ ] Includes a section capturing the team member's feedback upward
153- [ ] Ratings use the same scale applied to everyone in the same role
154- [ ] Anything termination-adjacent or compensation-related routed to HR or counsel before it is written
155 

Discussion

Alternatives

Skill CreatorCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Coding · Apache-2.0Professional Full-Stack Developer for Network Mapping & Monitoring ApplicationAct as a professional full-stack developer tasked with building a web application for mapping and monitoring networks using Mikrotik Netwatch API. Implement multi-user role-based management to handle devices, monitor their status, and manage user subscriptions.Coding · CC0-1.0Prompt refinerHigh-end Prompt Engineering & Prompt Refiner skill. Transforms raw or messy user requests into concise, token-efficient, high-performance master prompts for systems like GPT, Claude, and Gemini. Use when you want to optimize or redesign a prompt so it solves the problem reliably while minimizing tokens.Data & AI · CC0-1.0Constraint driven developmentEstablishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.Coding · MIT