automation-design
Skill4 starsChanged 3 months agoMITView on GitHub
Design Codex automations, scheduled research jobs, recurring reports, reminders, monitors, thread follow-ups, and workspace jobs. Use when the user asks to set up, improve, schedule, template, audit, or design an automation, monitor, reminder, or recurring Markdown report.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sidchaudhary/gtm-skillstheir own version, first seen Aug 21, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- sidchaudhary/gtm-skills★ 1same name
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 repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/project-docs-prep/templates/AGENTS.mdAGENTS.md
- skills/project-docs-prep/templates/CLAUDE.mdCLAUDE.md
- deep-planningSkill
- deep-planningSkill
- deprecatedSkill
- architecture-reviewSkill
- code-reviewSkill
- diagnoseSkill
- tddSkill
- ui-design-engineeringSkill
- ux-ui-design-assessmentSkill
- in-progressSkill
- mcp-tool-managementSkill
- skill-managementSkill
- obsidian-canvasSkill
- obsidian-markdownSkill
- obsidian-notion-bridgeSkill
- obsidian-vault-workflowSkill
- boomz-preferencesSkill
- personal-agent-workflowSkill
- personalSkill
- grill-with-docsSkill
- handoffSkill
- inbox-meeting-triageSkill
- markdown-reportSkill
- prompt-improvementSkill
- project-docs-prepSkill
- claim-citation-checkSkill
- daily-news-reportSkill
- github-skill-researchSkill
- project-discoverySkill
- repo-tourSkill
- research-methodologySkill
- seo-website-evaluatorSkill
- thaiSkill
- thai-addressSkill
- thai-customer-serviceSkill
- thai-date-formatSkill
- thai-festival-cardSkill
- thai-government-formSkill
- thai-id-validateSkill
- thai-invoiceSkill
- thai-pdpaSkill
- thai-resumeSkill
- thai-social-captionSkill
- thai-text-processingSkill
- thai-translateSkill
- backtest-expertSkill
- dividend-value-screenerSkill
- drawdown-circuit-breakerSkill
- exposure-coachSkill
- market-breadth-analyzerSkill
- portfolio-managerSkill
- position-sizerSkill
- tradingSkill
- trader-memory-coreSkill
- uptrend-analyzerSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Ask only when missing details would change the created automation.
- Distinctive: line 19
Write a self-contained prompt
- Distinctive: line 21
Keep schedule settings separate from task instructions.
- Distinctive: line 24
Use human-readable schedule language unless a tool requires structured syntax.
- Distinctive: line 28
When an automation tool is available and the user asked to create it, use the tool.
- Distinctive: line 29
If schedule or destination is missing, ask before creation.
- Distinctive: line 55
Prefer updating an existing automation over creating a duplicate.
- Distinctive: line 56
Use current-source tools for news, prices, laws, schedules, product releases, and other changing facts.
- Distinctive: line 57
Do not expose raw schedule syntax unless useful.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Automation Design
Design reliable automation prompts and schedules.
Workflow
- Identify automation type
- Choose reminder, thread follow-up, daily or weekly report, monitoring task, research digest, or workspace job.
- Capture requirements
- Clarify task, schedule, timezone, output destination, source rules, language, failure behavior, and whether duplicates should be suppressed.
- Ask only when missing details would change the created automation.
- Write a self-contained prompt
- Include goal, scope, sources or file boundaries, output format, quality rules, and missing-information behavior.
- Keep schedule settings separate from task instructions.
- Recommend schedule
- Use human-readable schedule language unless a tool requires structured syntax.
- State the timezone explicitly.
- Confirm or create
- When an automation tool is available and the user asked to create it, use the tool.
- If schedule or destination is missing, ask before creation.
Prompt Template
Task:
[What Codex should do]
Scope:
[Topics, files, repos, sources, or boundaries]
Quality rules:
- Use reliable sources or concrete local files.
- Include links or file paths.
- State uncertainty clearly.
- Avoid duplicate or low-value items.
Output:
[Markdown report, thread reply, file path, etc.]
Language and tone:
[Thai/English, concise/detailed]Rules
- Prefer updating an existing automation over creating a duplicate.
- Use current-source tools for news, prices, laws, schedules, product releases, and other changing facts.
- Do not expose raw schedule syntax unless useful.
- Report what will happen, when it will happen, and where the result will appear.
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.

