Menu
Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Analyze CSAT, NPS comments, reviews, and support feedback for sentiment, recurring themes, customer pain, and service improvement actions. Use for customer support and CX feedback reviews.
Create a concise daily briefing from calendar items, tasks, messages, and open decisions. Use at the start of a workday to identify priorities, risks, preparation needs, and follow-ups.
Turn business data, KPI movement, or experiment results into a clear narrative using the what-so what-now what structure, audience calibration, and action-oriented insight. Use when leaders need a data-backed brief, dashboard storyline, or metric interpretation. Do not use for raw statistical modeling with no communication deliverable.
Summarize document-heavy inputs such as memos, policies, PDFs, research notes, proposals, and multi-document packets. Use when users need key points, obligations, questions, and action implications from documents.
Draft clear, professional business emails from rough notes, context, or instructions. Handles cold outreach, internal updates, client responses, and escalation drafts. Use when the work is routine email writing with known context and audience. Do not use for sensitive legal notices, formal regulatory correspondence, or board-level communication without review.
Summarize meeting notes or transcripts into decisions, action items, owners, risks, and follow-up messages. Use after meetings when raw notes need a clean recap.
| name | codexkit-automation-designer |
| description | Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules. |
| version | 1.0.0 |
| category | automation |
Use this skill when a task should happen repeatedly and you need more than just a schedule.
Use references/automation-template.md as the default structure.
| Check | Question |
|---|---|
| Correctness | Does the workflow produce the expected output for the defined inputs? |
| Completeness | Are all trigger conditions, edge cases, and error paths handled? |
| Context-fit | Is the automation appropriate for the frequency and criticality of this task? |
| Consequence | If this ran unattended and failed silently, what would the downstream impact be? |
