Croft Airtable Task Creation
Use this skill to create task-like records in the Croft Airtable base. The caller must provide name; if it is missing or blank, ask before creating anything.
Read create workflow details for overrideable parameters, known task tables, view-hint behavior, request shape, and examples.
Defaults
- Base:
Croft -> appgRWEMtYCttCkjO
- Table:
Eng Backlog -> tbla72plmclVzubFK
- Assignee:
Will Akins -> usr6eB31TRW0oMiY5
- View hint:
Current Sprint by Assignee (2 weeks)
- Priority:
Low
- Status:
To Do
- Pipeline:
Current Sprint
Treat these as defaults, not hard-coded limits. Allow caller overrides for table, assignee, priority, status, pipeline, due date, acceptance criteria, tags, and requester.
Connector Behavior
- The Airtable connector does not expose view names or view ids.
- Treat
view_hint as semantic intent only.
- The connector rejected collaborator-field filtering in testing, so resolve assignee ids locally before writing.
- Use
typecast: true when creating records.
Workflow
- Resolve the base and table. Use known mappings first; inspect schema for unknown tables with
mcp__codex_apps__airtable._list_tables_for_base.
- Resolve the assignee. Default to Will. For another person, fetch a light table slice and match collaborator id, email, then case-insensitive display name. Ask if not confident.
- Build fields. Always set the table primary field from
name; add defaults or overrides for assignee, priority, status, and pipeline; add optional fields only when provided.
- Create the record with
mcp__codex_apps__airtable._create_records_for_table.
- Confirm what was created in a clean summary.
Field And Output Rules
- Do not create blank or placeholder-only records.
- Use the requested table's verified primary field.
- Add
Due By and Acceptance Criteria only when provided.
- Start with a one-line confirmation naming the task and table.
- Include effective assignee, priority, status, pipeline, view hint, and record id when returned.
- Mention when a named view was approximated.
- Do not dump raw schema or irrelevant field ids.
1---2name: airtable-create-croft-task3description: Create Croft Airtable tasks with defaults for Will Akins in Eng Backlog Current Sprint, low priority, and a current-sprint-by-assignee view hint. Use when Codex needs to create a new Airtable task and the caller provides the task name, with optional overrides for assignee, status, priority, pipeline, table, or other task fields.4---56# Croft Airtable Task Creation78Use this skill to create task-like records in the Croft Airtable base. The caller must provide `name`; if it is missing or blank, ask before creating anything.910Read [create workflow details](references/create-workflow.md) for overrideable parameters, known task tables, view-hint behavior, request shape, and examples.1112## Defaults1314- Base: `Croft` -> `appgRWEMtYCttCkjO`15- Table: `Eng Backlog` -> `tbla72plmclVzubFK`16- Assignee: `Will Akins` -> `usr6eB31TRW0oMiY5`17- View hint: `Current Sprint by Assignee (2 weeks)`18- Priority: `Low`19- Status: `To Do`20- Pipeline: `Current Sprint`2122Treat these as defaults, not hard-coded limits. Allow caller overrides for table, assignee, priority, status, pipeline, due date, acceptance criteria, tags, and requester.2324## Connector Behavior2526- The Airtable connector does not expose view names or view ids.27- Treat `view_hint` as semantic intent only.28- The connector rejected collaborator-field filtering in testing, so resolve assignee ids locally before writing.29- Use `typecast: true` when creating records.3031## Workflow32331. Resolve the base and table. Use known mappings first; inspect schema for unknown tables with `mcp__codex_apps__airtable._list_tables_for_base`.342. Resolve the assignee. Default to Will. For another person, fetch a light table slice and match collaborator id, email, then case-insensitive display name. Ask if not confident.353. Build fields. Always set the table primary field from `name`; add defaults or overrides for assignee, priority, status, and pipeline; add optional fields only when provided.364. Create the record with `mcp__codex_apps__airtable._create_records_for_table`.375. Confirm what was created in a clean summary.3839## Field And Output Rules4041- Do not create blank or placeholder-only records.42- Use the requested table's verified primary field.43- Add `Due By` and `Acceptance Criteria` only when provided.44- Start with a one-line confirmation naming the task and table.45- Include effective assignee, priority, status, pipeline, view hint, and record id when returned.46- Mention when a named view was approximated.47- Do not dump raw schema or irrelevant field ids.
willakins