Leave Management

Plan leave requests, approvals and balance records in the tool employees already use. The skill adds missing approval and balance steps rather than introducing a new system. It produces empty tracking templates on request.

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 a leave tracker, vacation tracker or absence register. Establish leave types, approvers, notice, handover, carry-over and whether days or balances are recorded.

It does not calculate country-specific leave entitlements or accrual rules. Approval and balance fields describe a workflow; they do not perform its calculations. 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 request, manager approval, calendar entry, balance update and report. Inputs identify participants, full-time or part-time work, the existing tool and whether approvals, balances or reporting are needed. Its 17 fields are Leave Request, Annual Leave Balance, Approver, Days Requested, Department, Emergency Contact, Employee Name, End Date, Handover Notes, Leave ID, Leave Type, Manager, Notes, Reason, Sick Leave Balance, Start Date and Status. Leave types include Annual, Sick, Casual, Unpaid, Maternity, Paternity and Comp Off. Statuses are Pending, Approved, Declined, Cancelled and Taken. No relation fields are specified.

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_leave_management_status ON leave_management (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.