Codex automation operator
Skill frankxai/starlight-automation-agent-skills/skills/codex-automation-operator
Portable automation agent skills for the Starlight substrate — scheduling, pipelines, and fleet ops.
npx -y skills add frankxai/starlight-automation-agent-skills --skill codex-automation-operatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Design and operate recurring Codex automations for scheduled reports, repo health, issue triage, inbox summaries, meeting briefs, deployment monitors, and agentic follow-up work. Use when a user asks to remember recurring work, schedule future Codex tasks, automate routine reviews, or decide whether a task belongs in Codex rather than Make.com, n8n, or MCP.
SKILL.md
1.5 KB, 265 tokens by cl100k_base, as published. Nobody here has run it
Codex Automation Operator
Use Codex automations for recurring work that needs judgment, synthesis, repo context, or connector-backed review.
Best Fit
- daily or weekly repo health summaries
- issue and PR triage
- Vercel preview checks
- inbox and calendar briefings
- partner follow-up drafts
- stale task reminders
- recurring public-safety scans
Use Another Tool When
- event latency matters more than reasoning: use Make.com or n8n
- a non-agent system must own execution: use n8n or Make.com
- the task is only a typed external tool call: use MCP
- the task needs multiple parallel repo workers: use a Starlight queue
Automation Spec
Return:
- name
- cadence
- scope
- sources/connectors
- output shape
- no-findings behavior
- archive behavior
- approval gates
- escalation condition
- owner and review cadence
Gates
Codex may draft, summarize, inspect, and report. Human approval is required before sending messages, posting publicly, spending, deleting, inviting, changing access, or production promotion.
Output Shape
Return: automation spec, why Codex is the owner, connectors needed, risk gates, and validation method.