Intern Program

Plan intern records from the initial offer through reviews, a certificate or a full-time offer. The skill starts with dates, a supervisor and mid-term and final scores. Conversion tracking is added only when interns actually convert.

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 internship management, an intern programme database, onboarding or conversion tracking. Clarify programme duration, mentor assignment, certificate requirements and conversion decisions.

It does not run an internship or assess intern performance on its own. A light employee record and progress log are the starting point; optional conversion fields should serve an actual 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 offer, intern record, mid review, final review, then certificate or offer. The 20-field reference covers intern identity, department, supervisor, mentor, school or university, programme type, start and end dates, duration, stipend and currency. It also includes learning goals, a weekly log link, mid-term and final scores, certificate and full-time-offer checkboxes, converted employee, status and Intern ID. Programme types include Internship, Apprenticeship, Graduate Program and Returnship; status progresses through Onboarding, In Progress, Completed or Terminated. There are no specified relation fields.

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_intern_program_status ON intern_program (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.