Agent skill

Performance Management

by sickn33 in sickn33/agentic-awesome-skills

Performance review register: review type, period, employee and reviewer, KPI, OKR and behaviour scores, overall rating, PIP and promotion flags, development plan.

MITAuto-check passedBusiness, Finance & HR

Install Performance Management

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill performance-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills performance-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/performance-management .claude/skills/performance-management && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
performance-management
GitHub stars
47k
Used in
1 other repo
Token cost
~4.1k tokens
SKILL.md length
1,440 words
Files
1
Skills in repo
1,354
Repo updated
First seen
Licence
MIT

At a glance

Performance review register: review type, period, employee and reviewer, KPI, OKR and behaviour scores, overall rating, PIP and promotion flags, development plan.

  • Works in 5 steps: Identify intent → Ask only what is missing → Hold the internal context → …
  • Performance reviews
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Field Reference, plus 9 more sections
  • Reaches json-schema.org

What it does

Performance Management is an agent skill from sickn33/agentic-awesome-skills. Performance review register: review type, period, employee and reviewer, KPI, OKR and behaviour scores, overall rating, PIP and promotion flags, development plan. Use for performance reviews.

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Business, Finance & HR, covering Performance reviews and OKRs and executive reporting. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Performance reviews
  • Tasks that involve Performance reviews
  • Tasks that involve OKRs and executive reporting

Example prompts

  • “/performance-management”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify intent
  2. Ask only what is missing
  3. Hold the internal context
  4. Recommend the smallest workflow
  5. Build only on request

What it can do on your machine

Read from SKILL.md and the folder at commit ec02547. 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 yaml, csv, sql, json and markdown).

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • json-schema.org

    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

Performance Management loads about 4.1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 1,440 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~4.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

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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 sickn33/agentic-awesome-skills at commit ec02547, republished under its MIT licence (© sickn33). 1,440 words, ~4,091 tokens.

Download SKILL.mdSave it as .claude/skills/performance-management/SKILL.md (or your agent's skills folder).
name
performance-management
description
Performance review register: review type, period, employee and reviewer, KPI, OKR and behaviour scores, overall rating, PIP and promotion flags, development plan. Use for performance reviews.
category
business
risk
safe
source
self
source_type
self
date_added
2026-09-26
author
WHOISABHISHEKADHIKARI
tags
sme, business, operations, database, csv, notion, sql, manage
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

Performance Management

What it is: Structured reviews.

Overview

Works out the smallest useful Performance Management setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

Layer: Layer 4: Manage. Fits: Growth stage. Table code: n/a.

When to Use This Skill

  • performance review
  • appraisal template
  • performance review cycle
  • employee review tracker

Also use it when the user says "structured reviews", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

  • "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
  • "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
  • "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
  • "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: How often do you review people?

Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a time, and stop as soon as the remaining answers would not change the output.

  • Cycle - How often? / Probation too? / Who reviews whom?
  • Content - Ratings or scores? / Goals plus feedback? / Development plan?
  • Process - Who signs off? / Shared with the person? / Appeals?
  • Current process - How do you review now? / Forms or documents? / Where stored?
  • Outcome - What do you need? / Forms, records or reporting?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless they ask, and it never carries a value the user did not give.

yaml
module: performance-management
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Cycle": null
  "Content": null
  "Process": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking
Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

Recommended approach: Build the review form around goals and behaviours already tracked elsewhere, and store the record per cycle.

Why this one: Reviews become paperwork when the review duplicates data you already track. Reference the KPI and OKR records instead of re-entering them.

Workflow: Review cycle → Self input → Manager review → Discussion → Record and actions

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the requested artifacts. For machine-readable text, keep prose outside the data; for files, provide a usable link. Report material validation failures or limitations separately.

A selected Notion output is rendered by notion-manual-import, so route the Notion step there. When the user selects Notion, hand that step to @notion-manual-import: it holds the CSV, the property mapping, the import steps and the verification checklist, and it renders the Field Reference below instead of defining a table of its own. Do not restate the mapping here and do not improvise the import steps. Manual CSV and mapping outputs need no connection. For requested workspace changes, follow the shared contract: verify actual tool access and the target before writing. A user saying "connected" is not tool evidence. Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user requests a workbook. A CSV carries no types, so after it, name the columns that need a number, date or currency format applied.

csv
Review Title,Areas for Improvement,Behaviour Score,Department,Development Plan,Due Date,Employee Name,Increment Recommended,KPI Score,Notes,OKR Score,Overall Rating,PIP Required,Promotion Eligible,Rating Label,Review Date,Review ID,Review Period,Review Type,Reviewer,Status,Strengths
Q1 review - Aarav Sharma,Delegation,4,Delivery,Lead one workstream,2026-01-15,Aarav Sharma,FALSE,82,Cycle opened in February; two reviewers have not submitted their notes yet.,0.7,4 - Exceeds Expectations,FALSE,FALSE,Strong,2026-01-15,,Q1 2026,Probation,Sneha Iyer,Manager Review,Reliable under pressure
sql
CREATE TABLE performance_management (
  review_title VARCHAR(255),
  areas_for_improvement VARCHAR(255),
  behaviour_score NUMERIC NOT NULL,
  department VARCHAR(255),
  development_plan VARCHAR(255),
  due_date DATE NOT NULL,
  employee_name VARCHAR(255),
  increment_recommended BOOLEAN NOT NULL,
  kpi_score NUMERIC NOT NULL,
  notes TEXT,
  okr_score NUMERIC NOT NULL,
  overall_rating VARCHAR(100) NOT NULL,
  pip_required BOOLEAN NOT NULL,
  promotion_eligible BOOLEAN NOT NULL,
  rating_label VARCHAR(255),
  review_date DATE NOT NULL,
  review_id SERIAL PRIMARY KEY,
  review_period VARCHAR(255),
  review_type VARCHAR(100) NOT NULL,
  reviewer VARCHAR(255),
  status VARCHAR(100) NOT NULL,
  strengths VARCHAR(255),
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_performance_management_status ON performance_management (status);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Performance Management",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Review Title": { "type": "string" },
      "Areas for Improvement": { "type": "string" },
      "Behaviour Score": { "type": "number" },
      "Department": { "type": "string" },
      "Development Plan": { "type": "string" },
      "Due Date": { "type": "string", "format": "date" },
      "Employee Name": { "type": "string" },
      "Increment Recommended": { "type": "boolean" },
      "KPI Score": { "type": "number" },
      "Notes": { "type": "string" },
      "OKR Score": { "type": "number" },
      "Overall Rating": { "type": "string" },
      "PIP Required": { "type": "boolean" },
      "Promotion Eligible": { "type": "boolean" },
      "Rating Label": { "type": "string" },
      "Review Date": { "type": "string", "format": "date" },
      "Review ID": { "type": "integer" },
      "Review Period": { "type": "string" },
      "Review Type": { "type": "string" },
      "Reviewer": { "type": "string" },
      "Status": { "type": "string" },
      "Strengths": { "type": "string" }
  },
  "required": [
      "Behaviour Score",
      "Due Date",
      "KPI Score",
      "OKR Score",
      "Overall Rating",
      "Review Date",
      "Review Type",
      "Status"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| Review Title | Title | Use as the database title |
| Areas for Improvement | Text | Leave as Text |
| Behaviour Score | Number | Convert to Number |
| Department | Text | Leave as Text |
| Development Plan | Text | Leave as Text |
| Due Date | Date | Convert to Date |
| Employee Name | Text | Leave as Text |
| Increment Recommended | Checkbox | Convert to Checkbox |
| KPI Score | Number | Convert to Number |
| Notes | Text | Leave as Text |
| OKR Score | Number | Convert to Number |
| Overall Rating | Select (add options after import) | Convert to Select, add options: "1 - Needs Improvement", "2 - Developing", "3 - Meets Expectations", "4 - Exceeds Expectations", "5 - Outstanding" |
| PIP Required | Checkbox | Convert to Checkbox |
| Promotion Eligible | Checkbox | Convert to Checkbox |
| Rating Label | Text | Leave as Text |
| Review Date | Date | Convert to Date |
| Review ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
| Review Period | Text | Leave as Text |
| Review Type | Select (add options after import) | Convert to Select, add options: "Probation", "Quarterly", "Half Yearly", "Annual", "Mid Term" |
| Reviewer | Text | Leave as Text |
| Status | Select (add options after import) | Convert to Select, add options: "Not Started", "Self Review", "Manager Review", "Calibration", "Finalised" |
| Strengths | Text | Leave as Text |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference

#FieldTypeSQLJSON SchemaNotionCSV example
1Review TitletextVARCHAR(255)stringTextQ1 review - Aarav Sharma
2Areas for ImprovementtextVARCHAR(255)stringTextDelegation
3Behaviour ScorenumberNUMERICnumberNumber4
4DepartmenttextVARCHAR(255)stringTextDelivery
5Development PlantextVARCHAR(255)stringTextLead one workstream
6Due DatedateDATEstring, format: dateDate2026-01-15
7Employee NametextVARCHAR(255)stringTextAarav Sharma
8Increment RecommendedcheckboxBOOLEANbooleanCheckboxFALSE
9KPI ScorenumberNUMERICnumberNumber82
10Noteslong_textTEXTstringTextCycle opened in February; two reviewers have not submitted their notes yet.
11OKR ScorenumberNUMERICnumberNumber0.7
12Overall RatingselectVARCHAR(100)stringSelect (add options after import)4 - Exceeds Expectations
13PIP RequiredcheckboxBOOLEANbooleanCheckboxFALSE
14Promotion EligiblecheckboxBOOLEANbooleanCheckboxFALSE
15Rating LabeltextVARCHAR(255)stringTextStrong
16Review DatedateDATEstring, format: dateDate2026-01-15
17Review IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
18Review PeriodtextVARCHAR(255)stringTextQ1 2026
19Review TypeselectVARCHAR(100)stringSelect (add options after import)Probation
20ReviewertextVARCHAR(255)stringTextSneha Iyer
21StatusselectVARCHAR(100)stringSelect (add options after import)Manager Review
22StrengthstextVARCHAR(255)stringTextReliable under pressure
Show full SKILL.md (496 more words)Show less

Select Options

Overall Rating

1 - Needs Improvement | 2 - Developing | 3 - Meets Expectations | 4 - Exceeds Expectations | 5 - Outstanding

Review Type

Probation | Quarterly | Half Yearly | Annual | Mid Term

Status

Not Started | Self Review | Manager Review | Calibration | Finalised

Relations

Link fields: none

Examples

Prompt

Reviews are done on forms nobody can find a year later.

Context first - one question per message, nothing already answered:

Q: How often? A: Half yearly.

Q: Ratings or scores? A: Both, 1 to 5.

Q: Where stored? A: Email.

Recommended next step - offered, not built:

Build the review form around goals and behaviours already tracked elsewhere, and store the record per cycle.

Workflow: Review cycle → Self input → Manager review → Discussion → Record and actions

Want the CSV, SQL, JSON Schema and Notion mapping for this?

Best Practices

  • Build when requested; recommend and offer a build for advice-only requests.
  • One question per message. A batched intake reads as a form and gets guessed at.
  • Keep display names identical across CSV and JSON; document normalized SQL identifiers.
  • Use relation for anything that points at another table, text only for free text.
  • Money fields are currency, never text. Dates are date, never free text.
  • If the user requests an example row, keep it obviously fake so nobody imports it as real data.

Limitations

  • Empty template only. It does not compute payroll, tax, leave balances or KPIs.
  • Notion relations need both databases imported before the link column resolves.
  • Select options are a starting set. Rename them to match how the business talks.
  • No automation, reminders or sync. Those need the integration layer.
  • Does not make promotion or pay decisions, and carries no legal standing on its own.
  • Legal, tax and HR review is still required before this drives real decisions.

Security & Safety Notes

  • Never fill in real names, salaries, medical or banking data. Placeholders only.
  • Label example rows as synthetic, and keep bank details masked.
  • Local reads, generation commands, and validation are part of a requested artifact build. External writes, messages, provisioning, and publication require authorization for that action and target; existing explicit authorization does not need to be repeated.
  • If sensitive data is supplied, avoid repeating unnecessary identifiers. Use only what the requested review needs; keep generated templates empty. Do not claim deletion from the conversation or service storage.
  • Privacy, legal and disciplinary cases need a qualified human reviewer before anything is acted on.

Common Pitfalls

  • Problem: a static mapping is described as a completed workspace build. Solution: deliver manual mappings without a connection; claim a live change only after the authorized tool operation succeeds.
  • Problem: asked all six questions in one message. Solution: ask one, wait, and drop any the first answer already covered.
  • Problem: built a full system when one table was asked for. Solution: build what was requested; mention the parent skill separately.
  • Problem: all four artifacts drift apart. Solution: derive all four from the field list in this file, never by hand.
  • Problem: Notion import shows every column as Text. Solution: that is expected. Apply the property mapping table once, after import.

Reusable Prompt

I want to set up structured reviews for my company.
Ask me one short question at a time, and only about what I have not already told you.
Then recommend the smallest setup that fits, and wait for me to ask before you build it.
When I ask, output CSV, SQL DDL, JSON Schema, a Notion property mapping or an Excel workbook. Data only.

© sickn33, 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/performance-management of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit ec02547

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Performance Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Performance Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Performance Management this skillsickn33/agentic-awesome-skills47k1 repos~4.1kAutomated safety check: PassMIT
Performance ReportAffitor/affiliate-skills6991 repos~2.5kAutomated safety check: PassMIT
65 Team Performance Review Globalminhnv0807/ai-business-skills608—~2.1kAutomated safety check: PassMIT
65 Team Performance Reviewminhnv0807/ai-business-skills608—~1.6kAutomated safety check: PassMIT
High Output Managementwondelai/skills2.4k—~5.1kAutomated safety check: PassMIT
Trading As Businessagentii-ai/agentii-investment-intelligence207—~655Automated safety check: PassApache-2.0

Similar skills

  • Performance Report

    Affitor/affiliate-skills

    Generate affiliate performance reports with KPIs and recommendations.

    699 GitHub starsUsed in 1 repo~2.5k tokens
    Business, Finance & HRAuto-check passed
  • 65 Team Performance Review Global

    minhnv0807/ai-business-skills

    A skill your agent uses 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…

    608 GitHub stars~2.1k tokensUpdated 26 days ago
    Business, Finance & HRAuto-check passed
  • 65 Team Performance Review

    minhnv0807/ai-business-skills

    Dung khi can danh gia CON NGUOI trong team marketing dua tren du lieu — KPI scorecard theo tung vai tro writer, designer, media buyer; diem manh co vi du that; diem can cai thien; development plan…

    608 GitHub stars~1.6k tokensUpdated 26 days ago
    Business, Finance & HRAuto-check passed
  • High Output Management

    wondelai/skills

    Manage for output using Grove's "High Output Management": a manager's output is their organization's output, raised by high-leverage activities.

    2.4k GitHub stars~5.1k tokensUpdated 27 days ago
    Business, Finance & HRAuto-check passed
  • Trading As Business

    agentii-ai/agentii-investment-intelligence

    Trading as a business, performance review process, trade journaling, capital allocation discipline, business infrastructure for traders, KPI tracking for trading operations

    207 GitHub stars~655 tokensUpdated 9 days ago
    Business, Finance & HRAuto-check passed
  • Send Report

    indranilbanerjee/digital-marketing-pro

    Generate a performance report from connected analytics MCPs (Google Analytics, Google/Meta/LinkedIn Ads, email platforms) and deliver it via Slack, email, or Google Sheets — weekly pulse, monthly…

    855 GitHub starsUsed in 1 repo~3.3k tokens
    Sales & SupportAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,354 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed
  • Content Creator

    sickn33/agentic-awesome-skills

    Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

Questions about Performance Management

What does Performance Management do?

Performance review register: review type, period, employee and reviewer, KPI, OKR and behaviour scores, overall rating, PIP and promotion flags, development plan. Performance Management is an agent skill from sickn33/agentic-awesome-skills. Performance review register: review type, period, employee and reviewer, KPI, OKR and behaviour scores, overall rating, PIP and promotion flags, development plan.

When should I use Performance Management?

Performance Management fits situations like: performance reviews; tasks that involve Performance reviews; tasks that involve OKRs and executive reporting.

How do I install Performance Management in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill performance-management -a claude-code`. Or copy the skill folder (skills/performance-management in sickn33/agentic-awesome-skills) into .claude/skills/performance-management in your project. Claude Code loads it when a task matches its description.

How do I install Performance Management in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill performance-management -a codex`. Or copy the skill folder (skills/performance-management in sickn33/agentic-awesome-skills) into .agents/skills/performance-management in your project. Codex loads it when a task matches its description.

Can I use Performance Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill performance-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/performance-management, .gemini/skills/performance-management, .github/skills/performance-management and .opencode/skills/performance-management in your project.

What does Performance Management need to run?

SKILL.md names no scripts, command-line tools or credentials: Performance Management is instructions for the agent only.

Does Performance Management access the network?

SKILL.md names 1 domain. In commands or code: json-schema.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Performance Management safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Performance Management use?

Performance Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Performance Management use?

About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Performance Management?

Skills that share tags, products or a category with Performance Management: Performance Report (Affitor/affiliate-skills, 699 stars), 65 Team Performance Review Global (minhnv0807/ai-business-skills, 608 stars), 65 Team Performance Review (minhnv0807/ai-business-skills, 608 stars) and High Output Management (wondelai/skills, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Performance Management?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,343 GitHub stars. The repository holds 1,354 skills in this directory. The repository was last updated on October 7, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.