65 Team Performance Review Global

What it does

When your agent uses it

• 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

Example prompts

• “performance review for my marketer”
• “evaluate a team member”
• “monthly 1:1 review”
• “/65-team-performance-review-global”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

1. 1Who is being reviewed, in what role, for what period? Content writer / designer / media buyer / channel owner; monthly or quarterly.
2. 2What 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. 3Concrete output data: pieces published, assets delivered, CPA/ROAS on campaigns they own, on-time rate, revisions per task.
4. 4Specific observations from the period: 2-3 real situations (positive and negative) with dates.

What it can do on your machine

Read from SKILL.md and the folder at commit 0360adc. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

65 Team Performance Review Global loads about 2.1k tokens when it runs. Until then it costs about 190 tokens; SKILL.md has 751 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~190

When it runs · the whole SKILL.md, loaded when a task matches

~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from minhnv0807/ai-business-skills at commit 0360adc, republished under its MIT licence (© minhnv0807). 751 words, ~2,127 tokens.

name

65-team-performance-review-global

description

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`.

metadata.version

1.0.1

metadata.category

operations

license

MIT

triggers

performance review, evaluate a team member, review my marketing team, monthly 1:1 review, feedback for a team member, development plan for an employee, KPI…

output

File .md — full review: KPI scorecard, strengths, areas to improve, 30/90-day development plan, rating rubric, next steps

related

64-team-brief-global, 63-campaign-retrospective-global, 07-marketing-report-global, 62-marketing-review-global, 47-design-review-global

# 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

© minhnv0807, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/en/65-team-performance-review-global of minhnv0807/ai-business-skills.

Open the folder on GitHubat commit 0360adc