Culture & Retention

Culture & Retention helps define a small set of employee engagement signals and a repeatable review process. Its workflow captures a signal, reviews it on a cadence, identifies a theme, records an action and checks the follow-up. It recommends periodic review over continuous measurement, with a quarterly review of a few signals as its example.

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 employee survey template, culture tracker, retention risk tracker or engagement survey results structure. It fits growth-stage businesses moving this process out of spreadsheets, documents or inboxes.

It produces empty templates and does not predict attrition or conduct engagement surveys. 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.

Inputs cover headcount, tenure, recent exits, current engagement or exit signals, ownership, review frequency and whether a survey is used. The requested outcome can be a signal tracker, survey or report. Fields include survey title, type and date, employee and department, anonymity, engagement, growth opportunity, happiness, manager relationship and work-life balance scores. Key concern, retention risk, responsible person, action plan, notes, status and culture ID provide the remaining record structure.

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_culture_retention_status ON culture_retention (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.