Agent skill

Course Upskilling Requests

by sickn33 in sickn33/agentic-awesome-skills

Training request register: course, provider, cost, duration, budget line, the three approval steps, service bond and completion evidence.

MITAuto-check passed

Install Course Upskilling Requests

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill course-upskilling-requests -a claude-code

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

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

At a glance

Training request register: course, provider, cost, duration, budget line, the three approval steps, service bond and completion evidence.

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

Course Upskilling Requests is an agent skill from sickn33/agentic-awesome-skills. Training request register: course, provider, cost, duration, budget line, the three approval steps, service bond and completion evidence. Use for upskilling approvals.

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

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

  • Upskilling approvals

Example prompts

  • “/course-upskilling-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

Course Upskilling Requests loads about 4k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 1,445 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
~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,445 words, ~4,029 tokens.

Download SKILL.mdSave it as .claude/skills/course-upskilling-requests/SKILL.md (or your agent's skills folder).
name
course-upskilling-requests
description
Training request register: course, provider, cost, duration, budget line, the three approval steps, service bond and completion evidence. Use for upskilling approvals.
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

Course & Upskilling Requests

What it is: Staff ask for a course, managers and finance approve, LMS tracks it.

Overview

Works out the smallest useful Course & Upskilling 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

  • training request form
  • upskilling request tracker
  • staff training request

Also use it when the user says "staff ask for a course, managers and finance approve, lms tracks it", 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: What is the training budget per person?

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.

  • Budget - Budget per person? / Annual pool or per request? / Currency?
  • Approval - Who approves? / Manager then finance? / Fast track under what amount?
  • After approval - Bond needed? / LMS or external? / Certificate tracked?
  • Current process - How do people ask now? / Email or form? / What gets lost?
  • Outcome - What do you need? / A request form, approvals or tracking?

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: course-upskilling-requests
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Budget": null
  "Approval": null
  "After 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: Route by cost, and record the decision. Tracking completion only matters if completion affects something.

Why this one: Training requests stall at approval, not at enrolment. A cost threshold with a named approver removes the bottleneck.

Workflow: Request → Manager approval → Finance approval → Enrolment → Completion and certificate

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,Course Name,Provider,Course Link,Linked Skill Gap,Reason,Cost,Currency,Duration (Hours),Start Date,Manager Approval,HR Approval,Finance Approval,Budget Line,Service Bond (Months),Enrolled in LMS,Completion Date,Certificate Received,Status,Course Request ID
Promotion to L3,Aarav Sharma,Delivery,Advanced SQL, Udemy,https://example.com/courses/safety,GAP-2026-003,Skill gap identified in the quarterly review,98000.00,INR,2.5,2026-01-15,FALSE,FALSE,FALSE,BL-114 Travel,12,FALSE,2026-01-15,FALSE,Approved,
sql
CREATE TABLE course_upskilling_requests (
  request_title VARCHAR(255),
  employee_name VARCHAR(255),
  department VARCHAR(255),
  course_name VARCHAR(255),
  provider VARCHAR(255),
  course_link TEXT,
  linked_skill_gap VARCHAR(255),  -- relation -> target record
  reason VARCHAR(255),
  cost NUMERIC(14,2) NOT NULL,
  currency VARCHAR(255),
  duration_hours NUMERIC NOT NULL,
  start_date DATE NOT NULL,
  manager_approval BOOLEAN NOT NULL,
  hr_approval BOOLEAN NOT NULL,
  finance_approval BOOLEAN NOT NULL,
  budget_line VARCHAR(255),
  service_bond_months NUMERIC NOT NULL,
  enrolled_in_lms BOOLEAN NOT NULL,
  completion_date DATE NOT NULL,
  certificate_received BOOLEAN NOT NULL,
  status VARCHAR(100) NOT NULL,
  course_request_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_course_upskilling_requests_status ON course_upskilling_requests (status);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Course & Upskilling Requests",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Request Title": { "type": "string" },
      "Employee Name": { "type": "string" },
      "Department": { "type": "string" },
      "Course Name": { "type": "string" },
      "Provider": { "type": "string" },
      "Course Link": { "type": "string", "format": "uri" },
      "Linked Skill Gap": { "type": "string" },
      "Reason": { "type": "string" },
      "Cost": { "type": "number" },
      "Currency": { "type": "string" },
      "Duration (Hours)": { "type": "number" },
      "Start Date": { "type": "string", "format": "date" },
      "Manager Approval": { "type": "boolean" },
      "HR Approval": { "type": "boolean" },
      "Finance Approval": { "type": "boolean" },
      "Budget Line": { "type": "string" },
      "Service Bond (Months)": { "type": "number" },
      "Enrolled in LMS": { "type": "boolean" },
      "Completion Date": { "type": "string", "format": "date" },
      "Certificate Received": { "type": "boolean" },
      "Status": { "type": "string" },
      "Course Request ID": { "type": "integer" }
  },
  "required": [
      "Cost",
      "Duration (Hours)",
      "Start Date",
      "Service Bond (Months)",
      "Completion 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 |
| Course Name | Text | Leave as Text |
| Provider | Text | Leave as Text |
| Course Link | URL | Convert to URL |
| Linked Skill Gap | Relation (link to the target database) | Convert to Relation, link to the target database |
| Reason | Text | Leave as Text |
| Cost | Number (format: currency) | Convert to Number, set format to Currency |
| Currency | Text | Leave as Text |
| Duration (Hours) | Number | Convert to Number |
| Start Date | Date | Convert to Date |
| Manager Approval | Checkbox | Convert to Checkbox |
| HR Approval | Checkbox | Convert to Checkbox |
| Finance Approval | Checkbox | Convert to Checkbox |
| Budget Line | Text | Leave as Text |
| Service Bond (Months) | Number | Convert to Number |
| Enrolled in LMS | Checkbox | Convert to Checkbox |
| Completion Date | Date | Convert to Date |
| Certificate Received | Checkbox | Convert to Checkbox |
| Status | Select (add options after import) | Convert to Select, add options: "Requested", "Approved", "Scheduled", "In Progress", "Completed", "Rejected" |
| Course Request 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
4Course NametextVARCHAR(255)stringTextAdvanced SQL
5ProvidertextVARCHAR(255)stringText Udemy
6Course LinkurlTEXTstring, format: uriURLhttps://example.com/courses/safety
7Linked Skill GaprelationVARCHAR(255)stringRelation (link to the target database)GAP-2026-003
8ReasontextVARCHAR(255)stringTextSkill gap identified in the quarterly review
9CostcurrencyNUMERIC(14,2)numberNumber (format: currency)98000.00
10CurrencytextVARCHAR(255)stringTextINR
11Duration (Hours)numberNUMERICnumberNumber2.5
12Start DatedateDATEstring, format: dateDate2026-01-15
13Manager ApprovalcheckboxBOOLEANbooleanCheckboxFALSE
14HR ApprovalcheckboxBOOLEANbooleanCheckboxFALSE
15Finance ApprovalcheckboxBOOLEANbooleanCheckboxFALSE
16Budget LinetextVARCHAR(255)stringTextBL-114 Travel
17Service Bond (Months)numberNUMERICnumberNumber12
18Enrolled in LMScheckboxBOOLEANbooleanCheckboxFALSE
19Completion DatedateDATEstring, format: dateDate2026-01-15
20Certificate ReceivedcheckboxBOOLEANbooleanCheckboxFALSE
21StatusselectVARCHAR(100)stringSelect (add options after import)Approved
22Course Request IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
Show full SKILL.md (488 more words)Show less

Select Options

Status

Requested | Approved | Scheduled | In Progress | Completed | Rejected

Relations

Link fields: Linked Skill Gap

Examples

Prompt

Course requests come by email and get lost in the thread.

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

Q: Budget per person? A: Around 2,000 a year.

Q: Who approves? A: Manager and finance.

Q: Tracked now? A: Only in email.

Recommended next step - offered, not built:

Route by cost, and record the decision. Tracking completion only matters if completion affects something.

Workflow: Request → Manager approval → Finance approval → Enrolment → Completion and certificate

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 deliver courses or manage an LMS.
  • 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 staff ask for a course, managers and finance approve, lms tracks it 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/course-upskilling-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

Course Upskilling 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.

Course Upskilling Requests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Course Upskilling Requests this skillsickn33/agentic-awesome-skills47k1 repos~4kAutomated safety check: PassMIT
Cost Budget Checkruvnet/ruflo74k—~645Automated safety check: NotesMIT
Cost Trackingaffaan-m/ECC276k1 repos~1.3kAutomated safety check: PassMIT
Cost Summaryruvnet/ruflo74k—~594Automated safety check: NotesMIT
Cost Conversationruvnet/ruflo74k—~407Automated safety check: NotesMIT
Cost Healthruvnet/ruflo74k—~901Automated safety check: NotesMIT

Similar skills

  • Cost Budget Check

    ruvnet/ruflo

    Read accumulated cost-tracking spend + budget config, compute utilization, emit 50/75/90/100% alert ladder

    74k GitHub stars~645 tokensUpdated today
    AI & LLM EngineeringAuto-check: notes
  • Cost Tracking

    affaan-m/ECC

    Track and report Claude Code token usage, spending, and budgets from the local ECC cost-tracker metrics log.

    276k GitHub starsUsed in 1 repo~1.3k tokens
    AI & LLM EngineeringAuto-check passed
  • Cost Summary

    ruvnet/ruflo

    Single-shot programmatic dump of all cost data — total spend, per-tier, top session, budget status, federation aggregate.

    74k GitHub stars~594 tokensUpdated today
    Auto-check: notes
  • Cost Conversation

    ruvnet/ruflo

    Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost

    74k GitHub stars~407 tokensUpdated today
    AI & LLM EngineeringAuto-check: notes
  • Cost Health

    ruvnet/ruflo

    Composite CI gate — runs cost-budget-check + cost-burn + cost-anomaly + cost-projection in parallel and surfaces a single combined health status with max exit code.

    74k GitHub stars~901 tokensUpdated today
    Auto-check: notes
  • Cost Report

    ruvnet/ruflo

    Generate a cost report showing token usage and USD costs by agent and model

    74k GitHub stars~830 tokensUpdated today
    AI & LLM EngineeringAuto-check: notes

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 Course Upskilling Requests

What does Course Upskilling Requests do?

Training request register: course, provider, cost, duration, budget line, the three approval steps, service bond and completion evidence. Course Upskilling Requests is an agent skill from sickn33/agentic-awesome-skills. Training request register: course, provider, cost, duration, budget line, the three approval steps, service bond and completion evidence.

When should I use Course Upskilling Requests?

Course Upskilling Requests fits situations like: upskilling approvals.

How do I install Course Upskilling Requests in Claude Code?

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

How do I install Course Upskilling Requests in Codex?

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

Can I use Course Upskilling 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 course-upskilling-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/course-upskilling-requests, .gemini/skills/course-upskilling-requests, .github/skills/course-upskilling-requests and .opencode/skills/course-upskilling-requests in your project.

What does Course Upskilling Requests need to run?

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

Does Course Upskilling 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 Course Upskilling 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 Course Upskilling Requests use?

Course Upskilling 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 Course Upskilling Requests use?

About 4k 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 Course Upskilling Requests?

Skills that share tags, products or a category with Course Upskilling Requests: Cost Budget Check (ruvnet/ruflo, 74k stars), Cost Tracking (affaan-m/ECC, 276k stars), Cost Summary (ruvnet/ruflo, 74k stars) and Cost Conversation (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Course Upskilling 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.