Learning & Career Development

Plan per-person learning records for enrolment, completion and certificates. The skill recommends completion dates and certificate links for later probation or promotion reviews. Mandatory flags are added only when the requirement is actually enforced.

The skill separates advice, review, conversion and build requests before producing artifacts. Advice receives a short recommendation and an offer of a relevant build. An explicit build request proceeds once essential missing facts are resolved. It asks one question at a time, reuses answers already supplied and stops when further answers would not change the deliverable. Unknown information remains unknown rather than receiving invented values.

Use it for an LMS tracker, course completion tracker or employee training record. Clarify internal or external learning, approvals, budgets, certificate tracking and the existing LMS.

It does not host courses or send learners anywhere. The output is a record structure, and mandatory tracking should reflect an actual requirement. The skill does not calculate payroll, tax, leave balances or KPIs. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review is required before templates drive real decisions.

The workflow is enrolment, progress, completion, certificate and record. Its 19 fields cover Course / Training, Certificate Earned, Completion Date, Course Category, Course URL, Delivery Method, Department, Duration (Hours), Employee Name and Course Request. LMS ID, Mandatory, Notes, Progress %, Provider, Score, Skills Gained, Start Date and Status complete the record. Course Request is the relation field. Categories are General, Operations, Finance, People and Compliance; statuses are Not Started, Enrolled, In Progress, Completed, Failed and Expired. Inputs establish who participates, whether completion is required and whether the desired output is a record, dashboard structure or mandatory tracking.

Requested artifacts can include CSV, SQL DDL, JSON Schema, Notion property mappings or an Excel workbook. The formats derive from one field list: CSV and JSON retain matching display names, while SQL uses normalized identifiers. Dates retain date types, money retains currency types and cross-table references retain relation types. Select options are a starting set that can be renamed to match the business.

One SQL example is:

CREATE INDEX idx_learning_career_development_status ON learning_career_development (status);

Templates are empty by default. Example rows are produced only on request and remain obviously synthetic. Sensitive identifiers should not be repeated unnecessarily during a requested review. Machine-readable data stays separate from explanatory prose and any material validation failures. Excel-compatible CSV uses UTF-8 with a byte order mark and accompanying guidance about number, date and currency columns. An XLSX workbook is a separate requested output rather than a renamed CSV.

The Notion output routes to notion-manual-import for CSV, property mappings, import steps and verification. Manual mappings require no connection. Requested live workspace changes require actual tool access, a verified target and authorization. Imported columns may initially be Text and need their mapped property types applied. Relation links resolve after both relevant databases are imported. A static mapping alone does not establish a completed workspace change.