628 skills · sorted by relevance
Turn a recurring workflow into an agent skill, or improve an existing one. Draft instructions, compare test outputs against a baseline, review quality and resource usage, and refine the description that determines when the skill is invoked.
Turn recurring workflows into Agent Skills, reusable instructions stored in SKILL.md. Guides checks for existing alternatives, scope selection, trigger wording, supporting files, evaluation, and distribution to editors through OpenKnowledge, with separate handling for skill distribution repositories.
Analyze public comments and replies to uncover recurring questions, complaints, objections, and buying signals. Get themes supported by exact quotes, plus ideas for content, FAQs, copy, or product improvements, with sample size and confidence stated.
Turn recurring work into a defined Grok Bot role and a setup prompt ready to paste into the app. Clarify tools, workflow, schedule, approval requirements, and a first task to test the role.
Review a project’s past Codex sessions, saved memory, and existing skills to identify recurring workflows. Receive prioritized recommendations for updating incomplete skills or creating distinct new ones, grounded in actual project history.
Review recent issues, pull requests, and recurring operational problems to choose a concrete repository improvement. Check for duplicate work, implement a suitable change, or document a plan and follow-up when implementation is blocked.
Analyze batches of Chinese comments to summarize positive, neutral, and negative sentiment, recurring words and phrases, and requests, complaints, or questions. Get counts and representative examples to support content reviews and future topic planning.
Review saved session learnings to find recurring successes, failures, and decisions. Consolidates similar patterns, proposes reusable skills, rules, event-triggered actions, or agent updates, and creates approved changes with references to the source sessions.
Break down a complex problem into opposing needs, identify the central conflict and its dominant side, then choose a response. The analysis also highlights changing priorities and tensions that need monitoring as work progresses.
Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recurring payment systems.
The English summary is being prepared. Showing the original description.
Decide which of your recurring rituals to put on autopilot — and which to keep manual. Use when asked what to automate, how to set up recurring AI runs, which reports or briefings could run on a schedule, or to design an automation charter for a team. Produces a ritual inventory with automate/assist/keep-manual calls, guardrails per ritual, and a rollout order.
The English summary is being prepared. Showing the original description.
Detect recurring patterns using the Agent Monitor's workflow intelligence — toolFlow transitions (tool A → B frequency matrices), recurring workflow patterns, agent co-occurrence pairs, model delegation habits, error propagation paths by agent depth, and compaction triggers. Use to discover habitual usage patterns and anti-patterns.
The English summary is being prepared. Showing the original description.
When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.
The English summary is being prepared. Showing the original description.
When you want to set up an agent loop, cron-scheduled task, or recurring workflow that runs autonomously. Judgment layer on top of Claude Code's ScheduleWakeup, CronCreate, and /loop — or, on other hosts, cron/GitHub Actions plus a headless agent CLI. Picks dynamic pacing, fixed cron, or a one-shot loop; designs idempotent loop bodies; sets bail-out conditions so loops don't run forever. Examples — weekly review pulse, daily brief, hourly metric monitor, periodic vault compile, upstream-check for an adapted skill. Triggers on "/loopify," "set up a loop," "schedule this task," "run this daily," "run this weekly," "cron this," "make this recurring," "automate this on a schedule," "keep this running until X." Part of the -ify trifecta (skillify / toolify / loopify). NOT for authoring a new skill — that's skillify. NOT for adding a tool/integration — that's toolify.
The English summary is being prepared. Showing the original description.
Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recurring payment systems.
The English summary is being prepared. Showing the original description.
Integrate with Google Calendar and Microsoft Outlook Calendar for scheduling, event management, and availability tracking. Use when someone asks to "create calendar events", "check availability", "schedule meetings", "sync calendars", "Google Calendar API", "Outlook Calendar API", "booking system", "find free slots", or "manage recurring events". Covers Google Calendar API v3, Microsoft Graph Calendar API, event CRUD, availability/free-busy queries, recurring events, and building scheduling features.
The English summary is being prepared. Showing the original description.
Guides you through setting up your first automatic task in Cowork — picking the right one, configuring the schedule, and making sure it runs correctly. For enabling background automation while you focus on other work, when setting up recurring morning briefings or end-of-day summaries, or during an automation setup session. Use when the user says "schedule a task", "automate something", "run this every day", "recurring task", "first scheduled task", "daily automation", or "can cowork do something automatically".
The English summary is being prepared. Showing the original description.
Write recurring newsletter issues with a consistent format and POV using the Curiosity Gap (George Loewenstein) and David Perell's Online Writing framework. Different from one-off emails (use /content-writer or /email-nurture). Use when the user asks for a newsletter, weekly/monthly newsletter, "write this week's issue", recurring email, Substack issue, internal newsletter, or any periodic publication with subscribers. Reads brand voice and content library from knowledge/. For a nurture or lifecycle sequence, see email-nurture. For long-form thought leadership, see thought-leadership-writer. For the monthly plan, see social-calendar.
The English summary is being prepared. Showing the original description.
Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recurring payment systems.
The English summary is being prepared. Showing the original description.
Cycle-end retrospective converting recurring judgment failures into durable enforcement. Reviews the cycle's friction — repeated user corrections, guard trips, RCA themes, integrate failures — and turns each recurring one into a landmines.md entry, then proposes graduation candidates up the enforcement funnel (landmine → advisory hook → hard gate). Pairs with standup: standup says what shipped and what's next; retrospective says what kept going wrong and how to stop it structurally. Writes only memory entries and a report — graduation proposals are advisory and require the normal seed.md amendment path to become enforcement. Invoke at the end of a release cycle, an epic, or any stretch of work with repeated friction.
The English summary is being prepared. Showing the original description.
Run a Codex prompt on a cron schedule or at a specific future time. Codex app Automations is the official, always-on surface for durable recurring schedules — recommend it FIRST; this local skill is a terminal fallback that only fires while its daemon runs. Triggers include "/schedule", "cron", "every Monday 9am", "run this at 3pm", "schedule a codex prompt", "recurring codex task", and one-time future runs ("run once at 3pm", "remind me to check X tomorrow"). For fixed-interval repeats ("every N minutes"), use the separate `loop` skill instead.
The English summary is being prepared. Showing the original description.
Design and review Action Scheduler jobs in WordPress plugins using Action Scheduler 3.9.x public APIs - async, single, recurring, and cron-expression actions; action_scheduler_init load timing; hook/args/group naming; unique and priority parameters; idempotent callbacks; chunked workloads; activation/deactivation cleanup; WooCommerce-bundled or standalone dependency usage; admin and WP-CLI debugging; queue runner limits; and safe operational troubleshooting. Use when a plugin schedules background jobs with as_enqueue_async_action, as_schedule_single_action, as_schedule_recurring_action, as_schedule_cron_action, as_get_scheduled_actions, or integrates with WooCommerce background queues.
The English summary is being prepared. Showing the original description.
When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.
The English summary is being prepared. Showing the original description.
Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recurring payment systems.
The English summary is being prepared. Showing the original description.