Agent skill

Promotion Upgrade Requests

by sickn33 in sickn33/agentic-awesome-skills

Promotion register: current and requested role and grade, justification, OKR and behaviour scores, time in role, salary proposal and decision.

MITAuto-check passedBusiness, Finance & HR

Install Promotion Upgrade Requests

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill promotion-upgrade-requests -a claude-code

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

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills promotion-upgrade-requests --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/promotion-upgrade-requests .claude/skills/promotion-upgrade-requests && 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
promotion-upgrade-requests
GitHub stars
47k
Used in
1 other repo
Token cost
~4.4k tokens
SKILL.md length
1,530 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Promotion register: current and requested role and grade, justification, OKR and behaviour scores, time in role, salary proposal and decision.

  • Works in 5 steps: Identify intent → Ask only what is missing → Hold the internal context → …
  • Upgrade requests
  • 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

Promotion Upgrade Requests is an agent skill from sickn33/agentic-awesome-skills. Promotion register: current and requested role and grade, justification, OKR and behaviour scores, time in role, salary proposal and decision. Use for upgrade requests.

Its SKILL.md is about 4.4k 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 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

  • Upgrade requests
  • Tasks that involve OKRs and executive reporting

Example prompts

  • “/promotion-upgrade-requests”

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

Promotion Upgrade Requests loads about 4.4k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 1,530 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~4.4k

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 b84d35a, republished under its MIT licence (© sickn33). 1,530 words, ~4,354 tokens.

Download SKILL.mdSave it as .claude/skills/promotion-upgrade-requests/SKILL.md (or your agent's skills folder).
name
promotion-upgrade-requests
description
Promotion register: current and requested role and grade, justification, OKR and behaviour scores, time in role, salary proposal and decision. Use for upgrade requests.
category
business
risk
safe
source
self
source_type
self
date_added
2026-09-26
author
WHOISABHISHEKADHIKARI
tags
sme, business, operations, database, csv, notion, sql, develop
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

Promotion & Upgrade Requests

What it is: Promotion, grade upgrade, role change and salary revision requests.

Overview

Works out the smallest useful Promotion & Upgrade Requests 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 5: Develop. Fits: Growth stage. Table code: n/a.

When to Use This Skill

  • promotion request
  • grade upgrade tracker
  • salary revision request
  • internal mobility tracker

Also use it when the user says "promotion, grade upgrade, role change and salary revision requests", 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: Who can request a promotion?

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.

  • Requests - ask these as separate messages, in this order when still material: who requests; how often; whether the request includes a grade or role change. Never combine two of them into one clarification. For an ambiguous Requests answer, clarify who may request first, then wait.
  • Criteria - Fixed criteria? / Performance score needed? / Time in role?
  • Approval - Who approves? / One or two levels? / Effective date set by?
  • Current process - How do you handle it now? / Email or nothing? / What gets delayed?
  • Outcome - What do you need? / A request form, approvals or a record?

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: promotion-upgrade-requests
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Requests": null
  "Criteria": null
  "Approval": 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: Require a written request with evidence, route it by grade, and record the decision and effective date as one object.

Why this one: Promotion decisions drift when the request, the evidence and the decision live in different places. One record with a decision field fixes the trail.

Workflow: Request submitted → Criteria check → Approval → Decision → People and payroll update

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
Request Title,Employee Name,Department,Request Type,Current Job Title,Current Grade,Requested Job Title,Requested Grade,Requested By,Justification,Linked Performance Review,OKR Score,Behaviour Score,Courses Completed,Time in Role (Months),Criteria Met,Current Salary,Proposed Salary,Currency,Increase %,Approver,Decision,Effective Date,Status,Upgrade ID
Promotion to L3,Aarav Sharma,Delivery,Promotion,HR Executive,L2,Finance Analyst,L3,Rohit Verma,Consistent delivery over 12 months,REV-2026-Q1,0.7,4,"Advanced SQL, Workplace Safety",18,FALSE,1450000.00,1624000.00,INR,12,Sneha Iyer,Approved,2026-01-15,Under Review,
sql
CREATE TABLE promotion_upgrade_requests (
  request_title VARCHAR(255),
  employee_name VARCHAR(255),
  department VARCHAR(255),
  request_type VARCHAR(100) NOT NULL,
  current_job_title VARCHAR(255),
  current_grade VARCHAR(255),
  requested_job_title VARCHAR(255),
  requested_grade VARCHAR(255),
  requested_by VARCHAR(255),
  justification VARCHAR(255),
  linked_performance_review VARCHAR(255),  -- relation -> target record
  okr_score NUMERIC NOT NULL,
  behaviour_score NUMERIC NOT NULL,
  courses_completed VARCHAR(255),
  time_in_role_months NUMERIC NOT NULL,
  criteria_met BOOLEAN NOT NULL,
  current_salary NUMERIC(14,2) NOT NULL,
  proposed_salary NUMERIC(14,2) NOT NULL,
  currency VARCHAR(255),
  increase_pct NUMERIC NOT NULL,
  approver VARCHAR(255),
  decision VARCHAR(255),
  effective_date DATE NOT NULL,
  status VARCHAR(100) NOT NULL,
  upgrade_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_promotion_upgrade_requests_status ON promotion_upgrade_requests (status);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Promotion & Upgrade Requests",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Request Title": { "type": "string" },
      "Employee Name": { "type": "string" },
      "Department": { "type": "string" },
      "Request Type": { "type": "string" },
      "Current Job Title": { "type": "string" },
      "Current Grade": { "type": "string" },
      "Requested Job Title": { "type": "string" },
      "Requested Grade": { "type": "string" },
      "Requested By": { "type": "string" },
      "Justification": { "type": "string" },
      "Linked Performance Review": { "type": "string" },
      "OKR Score": { "type": "number" },
      "Behaviour Score": { "type": "number" },
      "Courses Completed": { "type": "string" },
      "Time in Role (Months)": { "type": "number" },
      "Criteria Met": { "type": "boolean" },
      "Current Salary": { "type": "number" },
      "Proposed Salary": { "type": "number" },
      "Currency": { "type": "string" },
      "Increase %": { "type": "number" },
      "Approver": { "type": "string" },
      "Decision": { "type": "string" },
      "Effective Date": { "type": "string", "format": "date" },
      "Status": { "type": "string" },
      "Upgrade ID": { "type": "integer" }
  },
  "required": [
      "Request Type",
      "OKR Score",
      "Behaviour Score",
      "Time in Role (Months)",
      "Current Salary",
      "Proposed Salary",
      "Increase %",
      "Effective Date",
      "Status"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| Request Title | Title | Use as the database title |
| Employee Name | Text | Leave as Text |
| Department | Text | Leave as Text |
| Request Type | Select (add options after import) | Convert to Select, add options: "Promotion", "Grade Upgrade", "Role Change", "Salary Revision" |
| Current Job Title | Text | Leave as Text |
| Current Grade | Text | Leave as Text |
| Requested Job Title | Text | Leave as Text |
| Requested Grade | Text | Leave as Text |
| Requested By | Text | Leave as Text |
| Justification | Text | Leave as Text |
| Linked Performance Review | Relation (link to the target database) | Convert to Relation, link to the target database |
| OKR Score | Number | Convert to Number |
| Behaviour Score | Number | Convert to Number |
| Courses Completed | Text | Leave as Text |
| Time in Role (Months) | Number | Convert to Number |
| Criteria Met | Checkbox | Convert to Checkbox |
| Current Salary | Number (format: currency) | Convert to Number, set format to Currency |
| Proposed Salary | Number (format: currency) | Convert to Number, set format to Currency |
| Currency | Text | Leave as Text |
| Increase % | Number | Convert to Number |
| Approver | Text | Leave as Text |
| Decision | Text | Leave as Text |
| Effective Date | Date | Convert to Date |
| Status | Select (add options after import) | Convert to Select, add options: "Submitted", "Under Review", "Approved", "Declined", "Implemented" |
| Upgrade ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |

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
1Request TitletextVARCHAR(255)stringTextPromotion to L3
2Employee NametextVARCHAR(255)stringTextAarav Sharma
3DepartmenttextVARCHAR(255)stringTextDelivery
4Request TypeselectVARCHAR(100)stringSelect (add options after import)Promotion
5Current Job TitletextVARCHAR(255)stringTextHR Executive
6Current GradetextVARCHAR(255)stringTextL2
7Requested Job TitletextVARCHAR(255)stringTextFinance Analyst
8Requested GradetextVARCHAR(255)stringTextL3
9Requested BytextVARCHAR(255)stringTextRohit Verma
10JustificationtextVARCHAR(255)stringTextConsistent delivery over 12 months
11Linked Performance ReviewrelationVARCHAR(255)stringRelation (link to the target database)REV-2026-Q1
12OKR ScorenumberNUMERICnumberNumber0.7
13Behaviour ScorenumberNUMERICnumberNumber4
14Courses CompletedtextVARCHAR(255)stringTextAdvanced SQL, Workplace Safety
15Time in Role (Months)numberNUMERICnumberNumber18
16Criteria MetcheckboxBOOLEANbooleanCheckboxFALSE
17Current SalarycurrencyNUMERIC(14,2)numberNumber (format: currency)1450000.00
18Proposed SalarycurrencyNUMERIC(14,2)numberNumber (format: currency)1624000.00
19CurrencytextVARCHAR(255)stringTextINR
20Increase %numberNUMERICnumberNumber12
21ApprovertextVARCHAR(255)stringTextSneha Iyer
22DecisiontextVARCHAR(255)stringTextApproved
23Effective DatedateDATEstring, format: dateDate2026-01-15
24StatusselectVARCHAR(100)stringSelect (add options after import)Under Review
25Upgrade IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
Show full SKILL.md (500 more words)Show less

Select Options

Request Type

Promotion | Grade Upgrade | Role Change | Salary Revision

Status

Submitted | Under Review | Approved | Declined | Implemented

Relations

Link fields: Linked Performance Review

Examples

Prompt

Promotions happen over email and the reasoning is lost.

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

Q: Who can request? A: Line managers.

Q: Criteria? A: Performance and time in role.

Q: How often? A: Twice a year.

Recommended next step - offered, not built:

Require a written request with evidence, route it by grade, and record the decision and effective date as one object.

Workflow: Request submitted → Criteria check → Approval → Decision → People and payroll update

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 decide promotions or change pay. It records and routes the request.
  • 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.
  • Module Catalog - find the relevant module, then read its skill.
  • @people-directory - the employee master record most modules link to.
  • @notification-reminder-hub - turns due dates in this module into reminders.

Reusable Prompt

I want to set up promotion, grade upgrade, role change and salary revision requests 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/promotion-upgrade-requests of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

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

Promotion Upgrade Requests 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.

Promotion Upgrade Requests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Promotion Upgrade Requests this skillsickn33/agentic-awesome-skills47k1 repos~4.4kAutomated safety check: PassMIT
Pine BacktesterTradersPost/pinescript-agents1701 repos~3.9kAutomated safety check: PassNone
Analytics Strategyrampstackco/claude-skills945—~2.4kAutomated safety check: PassMIT
Onboarding Plannerbpinheiroms/dotfiles108—~5.4kAutomated safety check: PassNone
Replit Decksanqiufong/slides-from-anything1321 repos~2.9kAutomated safety check: PassApache-2.0
Building Streamlit Dashboardsiusztinpaul/designing-real-world-ai-agents-workshop512—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Pine Backtester

    TradersPost/pinescript-agents

    Implements comprehensive backtesting and performance metrics.

    170 GitHub starsUsed in 1 repo~3.9k tokens
    Business, Finance & HRAuto-check passed
  • Analytics Strategy

    rampstackco/claude-skills

    Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.

    945 GitHub stars~2.4k tokensUpdated 4 days ago
    Business, Finance & HRAuto-check passed
  • Onboarding Planner

    bpinheiroms/dotfiles

    Plan high-conversion mobile app onboarding flows from scratch.

    108 GitHub stars~5.4k tokensUpdated 4 mo ago
    Business, Finance & HRAuto-check passed
  • Replit Deck

    sanqiufong/slides-from-anything

    Single-file horizontal-swipe HTML deck in the style of Replit Slides's landing-page template gallery.

    132 GitHub starsUsed in 1 repo~2.9k tokens
    Business, Finance & HRAuto-check passed
  • Building Streamlit Dashboards

    iusztinpaul/designing-real-world-ai-agents-workshop

    Building dashboards in Streamlit. An agent skill from iusztinpaul/designing-real-world-ai-agents-workshop.

    512 GitHub stars~1.1k tokensUpdated 4 mo ago
    Business, Finance & HRAuto-check passed
  • Massing Bim

    ibuilder/massing

    Drive a Massing BIM/AEC project from an AI agent over MCP — read a project's status, records, CDE, KPI and model-quality checks; run standards-compliance, schedule-risk, embodied-carbon, permit-…

    122 GitHub stars~1.1k tokensUpdated 2 days ago
    Business, Finance & HRAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 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
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k 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

Questions about Promotion Upgrade Requests

What does Promotion Upgrade Requests do?

Promotion register: current and requested role and grade, justification, OKR and behaviour scores, time in role, salary proposal and decision. Promotion Upgrade Requests is an agent skill from sickn33/agentic-awesome-skills. Promotion register: current and requested role and grade, justification, OKR and behaviour scores, time in role, salary proposal and decision.

When should I use Promotion Upgrade Requests?

Promotion Upgrade Requests fits situations like: upgrade requests; tasks that involve OKRs and executive reporting.

How do I install Promotion Upgrade Requests in Claude Code?

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

How do I install Promotion Upgrade Requests in Codex?

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

Can I use Promotion Upgrade Requests 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 promotion-upgrade-requests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/promotion-upgrade-requests, .gemini/skills/promotion-upgrade-requests, .github/skills/promotion-upgrade-requests and .opencode/skills/promotion-upgrade-requests in your project.

What does Promotion Upgrade Requests need to run?

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

Does Promotion Upgrade Requests 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 Promotion Upgrade Requests 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 Promotion Upgrade Requests use?

Promotion Upgrade Requests 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 Promotion Upgrade Requests use?

About 4.4k tokens (SKILL.md is roughly 17k 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 Promotion Upgrade Requests?

Skills that share tags, products or a category with Promotion Upgrade Requests: Pine Backtester (TradersPost/pinescript-agents, 170 stars), Analytics Strategy (rampstackco/claude-skills, 945 stars), Onboarding Planner (bpinheiroms/dotfiles, 108 stars) and Replit Deck (sanqiufong/slides-from-anything, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Promotion Upgrade Requests?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 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.