Internal Communication

Plan a structured internal communication log with clear channel ownership and cadence. The skill recommends consolidating channels before adding more. It builds empty records for messages, meetings and acknowledgements 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 internal comms log, meeting tracker, town hall minutes or communication record. Clarify who owns each channel, who writes updates, the schedule and any moderation rules.

It does not send messages or connect to chat platforms. Ownership and a consistent format are the starting point; the tracker records a process rather than executing communication. 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 assigns channel ownership, sets a cadence, drafts a message, records publication and tracks reading or acknowledgement. Inputs identify channels, groups, email use, standing sections and whether a channel list, cadence or templates are needed. Its 12 fields are Communication Title, Type, Date, Department, Host, Attendees, Agenda, Action Items, Follow-up Date, Meeting Link, Status and Communication ID. Types include Announcement, Update, Policy, Newsletter and Escalation. Status options are Draft, Scheduled, Sent, Acknowledged and Archived. 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_internal_communication_status ON internal_communication (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.