Autom Automation
ComposioHQ/awesome-claude-skills
Automate Autom tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Create and manage automations via the slay CLI. An agent skill from debuglebowski/slayzone.
GPL-3.0Auto-check passed
Install Slay Automations
$ npx skills add debuglebowski/slayzone --skill slay-automations -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install debuglebowski/slayzone slay-automations --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/debuglebowski/slayzone.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/slay-automations .claude/skills/slay-automations && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "slay-automations" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-automations into .claude/skills/slay-automations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-automations", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-automationsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add debuglebowski/slayzone --skill slay-automations -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install debuglebowski/slayzone slay-automations --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/debuglebowski/slayzone.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/slay-automations .agents/skills/slay-automations && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "slay-automations" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-automations into .agents/skills/slay-automations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-automations", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add debuglebowski/slayzone --skill slay-automations -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install debuglebowski/slayzone slay-automations --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/debuglebowski/slayzone.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/slay-automations .cursor/skills/slay-automations && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "slay-automations" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-automations into .cursor/skills/slay-automations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-automations", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/debuglebowski/slayzone.git --path .agents/skills/slay-automations--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add debuglebowski/slayzone --skill slay-automations -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install debuglebowski/slayzone slay-automations --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/debuglebowski/slayzone.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/slay-automations .gemini/skills/slay-automations && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "slay-automations" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-automations into .gemini/skills/slay-automations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-automations", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install debuglebowski/slayzone slay-automationsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add debuglebowski/slayzone --skill slay-automations -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/debuglebowski/slayzone.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/slay-automations .github/skills/slay-automations && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "slay-automations" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-automations into .github/skills/slay-automations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-automations", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add debuglebowski/slayzone --skill slay-automations -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install debuglebowski/slayzone slay-automations --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/debuglebowski/slayzone.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/slay-automations .opencode/skills/slay-automations && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "slay-automations" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-automations into .opencode/skills/slay-automations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-automations", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
slay-automations- GitHub stars
- 191
- Token cost
- ~627 tokens
- SKILL.md length
- 253 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Create and manage automations via the slay CLI. An agent skill from debuglebowski/slayzone.
- SKILL.md covers Trigger types, Commands and Config file example
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Slay Automations is an agent skill from debuglebowski/slayzone. Create and manage automations via the slay CLI
Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The licence is GPL-3.0.
Example prompts
- “/slay-automations”
What it can do on your machine
Read from SKILL.md and the folder at commit e912716. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Slay Automations loads about 627 tokens when it runs. Until then it costs about 16 tokens; SKILL.md has 253 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from debuglebowski/slayzone at commit e912716, republished under its GPL-3.0 licence (© debuglebowski). 253 words, ~627 tokens.
Download SKILL.mdSave it as
.claude/skills/slay-automations/SKILL.md (or your agent's skills folder).- name
- slay-automations
- description
- Create and manage automations via the slay CLI
- trigger
- auto
Automations are project-scoped, event-driven actions. They fire shell commands in response to task events or on a cron schedule.
Trigger types
| Type | Fires when | Extra flags |
|---|---|---|
task_status_change | Task status changes | --trigger-from-status, --trigger-to-status (both optional, filter transitions) |
task_created | New task created | — |
task_archived | Task archived | — |
task_tag_changed | Tags modified on a task | — |
cron | On schedule | --cron <expression> (required) |
manual | Only via slay automations run | — |
Commands
slay automations list --project <name|id> [--json]— list automations for a project.- Shows enabled state, trigger type, run count, and last run time
slay automations view <id> [--json]— view full automation details including trigger config, conditions, and actions.slay automations create <name> --project <name|id> --trigger <type> [--action-command <cmd>] [--trigger-from-status <status>] [--trigger-to-status <status>] [--cron <expression>] [--description <text>] [--config <file>]— create an automation.- For simple automations, use
--action-commandto specify a shell command - For complex setups with multiple actions or conditions, use
--config <file>with JSON{ trigger_config, conditions?, actions }— overrides all other flags
- For simple automations, use
slay automations update <id> [--name <n>] [--description <text>] [--enabled] [--disabled] [--trigger <type>] [--action-command <cmd>] [--trigger-from-status <s>] [--trigger-to-status <s>] [--cron <expr>]— update an automation.- At least one option required
slay automations delete <id>— permanently delete an automation.slay automations toggle <id>— flip the enabled/disabled state.- You don't need to know the current state — it toggles automatically
slay automations run <id>— manually trigger an automation.- Requires the SlayZone app to be running (uses the app's HTTP API)
- Reports status and duration
slay automations runs <id> [--limit <n>] [--json]— view execution history.- Shows status, duration, and any errors
- Default limit: 10
Config file example
{
"trigger_config": { "type": "task_status_change", "params": { "toStatus": "done" } },
"actions": [
{ "type": "run_command", "params": { "command": "echo 'Task completed!'" } }
]
}© debuglebowski, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/slay-automations of debuglebowski/slayzone.
Open the folder on GitHubat commit e912716
Compare with similar skills
Slay Automations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Slay Automations this skilldebuglebowski/slayzone | 191 | — | ~627 | Automated safety check: Pass | GPL-3.0 | |
| Autom AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~723 | Automated safety check: Pass | None | |
| Doppler Marketing Automation AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~809 | Automated safety check: Pass | None | |
| Suggest Automationsn8n-io/n8n | 207k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Aero Workflow AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~753 | Automated safety check: Pass | None | |
| Anchor Browser AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~757 | Automated safety check: Pass | None |
Similar skills
Doppler Marketing Automation Automation
ComposioHQ/awesome-claude-skills
Automate Doppler Marketing Automation tasks via Rube MCP (Composio).
- Official
Suggest Automations
n8n-io/n8n
Offer the three most common automations for a user as a single-choice card, from your own knowledge of their team and their apps, then build the one they choose once they confirm, or offer more.
Aero Workflow Automation
ComposioHQ/awesome-claude-skills
Automate Aero Workflow tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Anchor Browser Automation
ComposioHQ/awesome-claude-skills
Automate Anchor Browser tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
- Official
Automate This
github/awesome-copilot
Analyze a screen recording of a manual process and produce targeted, working automation scripts.
More from debuglebowski/slayzone
All 16 skills in this repoComparison Page
debuglebowski/slayzone
Create or update objective website comparison pages and head-to-head pages from the comparison canon.
Slay Artifacts
debuglebowski/slayzone
Manage task artifacts (files, folders) via the slay CLI. An agent skill from debuglebowski/slayzone.
Slay Orchestrate
debuglebowski/slayzone
Supervise a set of slay tasks through planning, execution, and verification
Slay Context
debuglebowski/slayzone
Ensure root instruction files include SlayZone environment context
Slay Pty
debuglebowski/slayzone
Interact with PTY terminal sessions via the slay CLI. An agent skill from debuglebowski/slayzone.
Commit
debuglebowski/slayzone
Commit the changes that has been worked on in this session. An agent skill from debuglebowski/slayzone.
Questions about Slay Automations
What does Slay Automations do?
Create and manage automations via the slay CLI. An agent skill from debuglebowski/slayzone. Slay Automations is an agent skill from debuglebowski/slayzone.
How do I install Slay Automations in Claude Code?
Run `npx skills add debuglebowski/slayzone --skill slay-automations -a claude-code`. Or copy the skill folder (.agents/skills/slay-automations in debuglebowski/slayzone) into .claude/skills/slay-automations in your project. Claude Code loads it when a task matches its description.
How do I install Slay Automations in Codex?
Run `npx skills add debuglebowski/slayzone --skill slay-automations -a codex`. Or copy the skill folder (.agents/skills/slay-automations in debuglebowski/slayzone) into .agents/skills/slay-automations in your project. Codex loads it when a task matches its description.
Can I use Slay Automations in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add debuglebowski/slayzone --skill slay-automations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slay-automations, .gemini/skills/slay-automations, .github/skills/slay-automations and .opencode/skills/slay-automations in your project.
What does Slay Automations need to run?
SKILL.md names no scripts, command-line tools or credentials: Slay Automations is instructions for the agent only.
Does Slay Automations access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Slay Automations safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Slay Automations use?
Slay Automations is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Slay Automations use?
About 627 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Slay Automations?
Skills that share tags, products or a category with Slay Automations: Autom Automation (ComposioHQ/awesome-claude-skills, 77k stars), Doppler Marketing Automation Automation (ComposioHQ/awesome-claude-skills, 77k stars), Suggest Automations (n8n-io/n8n, 207k stars) and Aero Workflow Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Slay Automations?
debuglebowski (a GitHub user) maintains it in debuglebowski/slayzone, which has 191 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 3, 2026.
Source: debuglebowski/slayzone on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.