65-team-performance-review-global
Skill644 starsChanged 6 months agoMITView on GitHub
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`.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- minhnv0807/ai-business-skillsword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- minhnv0807/ai-business-skills★ 644100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository134 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- 00-marketing-plan-globalSkill
- 01-content-calendar-globalSkill
- 02-campaign-brief-globalSkill
- 03-performance-eval-globalSkill
- 04-script-video-globalSkill
- 05-ad-copy-globalSkill
- 06-ugc-egc-brief-globalSkill
- 07-marketing-report-globalSkill
- 08-competitor-research-globalSkill
- 09-customer-insight-globalSkill
- 10-reverse-kpi-globalSkill
- 11-channel-setup-globalSkill
- 12-landing-page-brief-globalSkill
- 13-data-analysis-globalSkill
- 14-email-marketing-globalSkill
- 15-social-listening-globalSkill
- 16-marketing-psychology-globalSkill
- 17-pricing-strategy-globalSkill
- 18-referral-program-globalSkill
- 19-ab-test-setup-globalSkill
- 20-client-intake-brief-globalSkill
- 21-ads-audit-globalSkill
- 30-design-master-globalSkill
- 31-offer-design-globalSkill
- 32-seo-growth-globalSkill
- 33-b2b-lead-gen-globalSkill
- 34-ai-marketing-os-globalSkill
- 35-brand-voice-globalSkill
- 36-content-brief-globalSkill
- 37-social-caption-globalSkill
- 38-community-seeding-globalSkill
- 39-content-audit-globalSkill
- 40-next-content-plan-globalSkill
- 41-campaign-asset-list-globalSkill
- 42-image-brief-globalSkill
- 43-carousel-brief-globalSkill
- 44-video-editor-brief-globalSkill
- 45-design-tool-brief-globalSkill
- 46-brand-guideline-globalSkill
- 47-design-review-globalSkill
- 48-quick-visual-brief-globalSkill
- 49-html-email-template-globalSkill
- 50-asset-resize-globalSkill
- 51-audience-research-globalSkill
- 52-account-structure-globalSkill
- 53-tracking-setup-globalSkill
- 54-media-plan-globalSkill
- 55-scaling-ads-globalSkill
- 56-retargeting-plan-globalSkill
- 57-next-ads-plan-globalSkill
- 58-positioning-globalSkill
- 59-go-to-market-globalSkill
- 60-launch-playbook-globalSkill
- 61-budget-planning-globalSkill
- 62-marketing-review-globalSkill
- 63-campaign-retrospective-globalSkill
- 64-team-brief-globalSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Read the brief history (64-team-brief-global), last period's output, and the reports (07-marketing-report-global) if available.
- Distinctive: line 34
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.
- Distinctive: line 42
Assess behavior, not character: Write "submitted late 3 times without notice", not "irresponsible".
- Distinctive: line 52
Avoid subjective characterizations, comparisons to other individuals, and anything touching protected characteristics (age, gender, race, …
- Distinctive: line 53
Do not put speculation about a person's attitude, motives, personal circumstances, or health in the document.
- Distinctive: line 65
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.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
- Who is being reviewed, in what role, for what period? Content writer / designer / media buyer / channel owner; monthly or quarterly.
- 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.
- Concrete output data: pieces published, assets delivered, CPA/ROAS on campaigns they own, on-time rate, revisions per task.
- Specific observations from the period: 2-3 real situations (positive and negative) with dates.
Principles
- No surprises. Negative feedback is given when it happens, not saved for review day.
- Every statement needs evidence. "Hard-working" is not an assessment; "on time on 9 of 10 tasks, proposed two new content angles unprompted" is.
- Assess behavior, not character. Write "submitted late 3 times without notice", not "irresponsible".
- Rate consistently. Apply the same standard across the team; do not let personal rapport shift the scale.
- A review must produce a development plan. Without one it is just an unusable scorecard.
- 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 writing1: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.
Related skills
64-team-brief-global: source of on-time rate and revision counts.62-marketing-review-globaland47-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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

