Offer & Appointment

Plan a formal hiring record that connects an approved offer to onboarding. The skill prioritizes an offer record with version, approver and expiry over the document template. It builds empty records 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 an offer letter tracker, appointment record, hiring offer database or new-hire offer log. Clarify pay shape, equity, probation, notice, joining date, approval and signing process.

It does not generate contracts or send legally binding documents. Capturing offer information at the offer stage supports the recruiting-to-payroll handoff without executing either process. 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 approved offer, offer sent, candidate accepts, record created and onboarding started. Its 18 fields are Offer Title, Candidate Name, Recruitment Record, Position, Department, Grade Level, Employment Type, Offered Salary, Currency, Offer Date, Offer Expiry, Joining Date, Probation Period (Days), Approver, Signed Via, Status, Notes and Offer ID. Recruitment Record is the relation field. Grades start with L1 through L5, M1 and M2. Employment types include Full Time, Part Time, Contract, Intern and Consultant; statuses are Draft, Offered, Negotiation, Accepted, Declined, Withdrawn and Joined. Signed Via records the signing method rather than creating a signing-service integration.

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_offer_appointment_status ON offer_appointment (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.