Health & Wellness

Plan employee wellbeing benefits and participation tracking with privacy boundaries. The recommended workflow keeps uptake counts and anonymous feedback rather than individual health information. The skill produces empty 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 employee wellbeing, a health check-in tracker, wellness surveys or a mental health support log. Establish anonymity, visibility and whether any health details would be held before selecting fields.

It does not provide medical advice, coverage or a health service. Track benefits and uptake without storing individual health information; the wider example field reference is not an instruction to collect it. 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 setup asks about participants, programmes, whether participation is optional, existing communication and the desired benefits list or participation counts. Its recommended workflow is benefit offered, uptake count, anonymous feedback and review. The 13-field reference contains Check-in Title, Employee Name, Anonymous, Department, Check-in Date, Wellbeing Score, Stress Level, Energy Level, Support Requested, Resource Shared, Confidential, Status and Wellness ID. Stress levels range from Low to Critical; energy levels from Low to High. Confidentiality ranges from Public to Highly Restricted, and statuses include Scheduled, Completed, Missed and Follow-up Due. 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_health_wellness_status ON health_wellness (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.