course-upskilling-requests – Other skill for AI agents
Training request register: course, provider, cost, duration, budget line, the three approval steps, service bond and completion evidence. Use for upskilling approvals.
Install the course-upskilling-requests skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/course-upskilling-requests-38d73.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /course-upskilling-requests – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/course-upskilling-requests-38d73.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $course-upskilling-requests – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/course-upskilling-requests-38d73.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /course-upskilling-requests – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/course-upskilling-requests-38d73.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /course-upskilling-requests – then describe the task you want done.
SKILL.md content
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.
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 askingStep 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.
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,,FALSE,Requested,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,
manager_approval BOOLEAN NOT NULL,
hr_approval BOOLEAN NOT NULL,
finance_approval BOOLEAN NOT NULL,
budget_line VARCHAR(255),
service_bond_months INTEGER CHECK (service_bond_months >= 0),
enrolled_in_lms BOOLEAN NOT NULL,
completion_date DATE,
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);{
"$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",
"Currency",
"Manager Approval",
"HR Approval",
"Finance Approval",
"Enrolled in LMS",
"Certificate Received",
"Duration (Hours)",
"Status"
]
}| 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 | … (full content is in the download package)
Related skills
- create-issue-gate – Use when starting a new implementation task and an issue must be created with strict…
- cred-omega – CISO operacional enterprise para gestao total de credenciais e segredos.
- crossframe – Use when the user explicitly invokes CrossFrame or 跨尺度结构诊断 for Chinese-canonical…
- crossframe-casebook – Use when CrossFrame Suite routes explicit Chinese casebook work: turning materials into…
- crossframe-dialogue – Use when CrossFrame Suite routes explicit Chinese reader replies, editor responses…
- crossframe-teach – Use when CrossFrame Suite routes explicit Chinese teaching of CrossFrame concepts…
- csv-manual-export – CSV Manual Export: a UTF-8 CSV template from a confirmed field list, empty by default…
- ctr-predictor – CTR Predictor. Use when working with impressions and an explicitly supplied CTR…