automation
Skill1 starsChanged 7 days agoMITView on GitHub
Interactive guide to design and create a scheduled background automation. Use this skill when the user wants to create an automated or recurring scheduled task (e.g. "summarize my unread emails every morning", "every Monday send me a to-do list"). Also triggered by the /automation slash command.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- gkurt/ai-soulstheir own version, first seen Nov 8, 2026
- linxule/carreltheir own version, first seen Nov 8, 2026
- jstilb/ai-assistanttheir own version, first seen Oct 30, 2026
- harshsinghmp/muse-skillstheir own version, first seen Oct 15, 2026
- cutec-chris/PawLiatheir own version, first seen Oct 15, 2026
- vercel-labs/nativetheir own version, first seen Oct 13, 2026
Used with
Projects with it also use refactor and research.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- vercel-labs/zero-native★ 7.8ksame name
- vercel-labs/native★ 7.8ksame name
- proophboard/skills★ 6same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- linxule/carrel★ 2same name
- AHX47/claw-skills-any★ 1same name
- alizafarbati/opencode-agents-mcp★ 1same name
- cutec-chris/PawLia★ 1same name
- donatassimkus/claude-ai-skills★ 1same name
- harshsinghmp/muse-skills★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- code-reviewSkill
- generative-uiSkill
- github-workflowSkill
- react-expertSkill
- vlypse-guideSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Turn 1 — Cadence: Ask via ask_question (Hourly, Daily, Weekly, or Custom cron schedule).
- Very specific: line 13
Turn 2 — Time / Day: Ask for the specific time or day of week (ask_question).
- Distinctive: line 14
Turn 3 — Task Prompt: Ask what the agent should do on each run and refine into a clear, self-contained prompt.
- Distinctive: line 15
Turn 4 — Save Automation: Write the automation specification into the project or global automation config.
- Very specific: line 23
Use ask_question to confirm frequency: Hourly, Daily, Weekly, or Custom cron schedule.
- Distinctive: line 29
Ask the user for the prompt in plain text.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scheduled Automations
A scheduled automation runs on a cron schedule in the background and starts a fresh agent conversation or task on each run.
Quick Start (5-Turn Creation Flow)
- Turn 1 — Cadence: Ask via
ask_question(Hourly,Daily,Weekly, orCustom cron schedule). - Turn 2 — Time / Day: Ask for the specific time or day of week (
ask_question). - Turn 3 — Task Prompt: Ask what the agent should do on each run and refine into a clear, self-contained prompt.
- Turn 4 — Save Automation: Write the automation specification into the project or global automation config.
- Turn 5 — Test Run: Offer to run the prompt immediately to verify that tools and execution complete properly.
Interactive Creation Workflow
Guide the user through creating the automation one step at a time across turns. If the user already provided some details in their initial prompt (such as the schedule or the task), skip the questions already answered and proceed to the next missing step.
Turn 1: Ask for the Cadence
Use ask_question to confirm frequency: Hourly, Daily, Weekly, or Custom cron schedule.
Turn 2: Confirm Specific Time / Day
Based on cadence, confirm time of day and day of week.
Turn 3: Ask What the Task Should Do
Ask the user for the prompt in plain text.
Turn 4: Translate Schedule & Author Prompt
Standard 5-field cron expression:
- Hourly:
0 * * * * - Daily at 9 AM:
0 9 * * * - Weekdays at 9 AM:
0 9 * * 1-5
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.