MemPalace Task Handoff
MemPalace/mempalace
Creates, hands off, claims, executes and closes agent tasks through the MemPalace logstream, with approval of the exact task before it is recorded.
Manage tasks, subtasks, tags, and templates via the slay CLI
Install Slay Tasks
$ npx skills add debuglebowski/slayzone --skill slay-tasks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install debuglebowski/slayzone slay-tasks --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-tasks .claude/skills/slay-tasks && 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-tasks" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-tasks into .claude/skills/slay-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-tasks", 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-tasksType 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-tasks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install debuglebowski/slayzone slay-tasks --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-tasks .agents/skills/slay-tasks && 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-tasks" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-tasks into .agents/skills/slay-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-tasks", 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-tasks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install debuglebowski/slayzone slay-tasks --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-tasks .cursor/skills/slay-tasks && 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-tasks" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-tasks into .cursor/skills/slay-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-tasks", 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-tasks--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-tasks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install debuglebowski/slayzone slay-tasks --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-tasks .gemini/skills/slay-tasks && 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-tasks" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-tasks into .gemini/skills/slay-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-tasks", 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-tasksInstalls 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-tasks -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-tasks .github/skills/slay-tasks && 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-tasks" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-tasks into .github/skills/slay-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-tasks", 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-tasks -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-tasks --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-tasks .opencode/skills/slay-tasks && 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-tasks" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-tasks into .opencode/skills/slay-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-tasks", 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-tasks- GitHub stars
- 191
- Token cost
- ~1.6k tokens
- SKILL.md length
- 805 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Manage tasks, subtasks, tags, and templates via the slay CLI
- Tasks that involve Task breakdown
- SKILL.md covers Task lifecycle, Subtasks, Blocking and Task tags, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Slay Tasks is an agent skill from debuglebowski/slayzone. Manage tasks, subtasks, tags, and templates via the slay CLI
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Task breakdown. The licence is GPL-3.0.
When your agent uses it
- Tasks that involve Task breakdown
Example prompts
- “/slay-tasks”
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.
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 Tasks loads about 1.6k tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 805 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). 805 words, ~1,601 tokens.
Download SKILL.mdSave it as
.claude/skills/slay-tasks/SKILL.md (or your agent's skills folder).- name
- slay-tasks
- description
- Manage tasks, subtasks, tags, and templates via the slay CLI
- trigger
- auto
Task commands are the core of the slay CLI. Most commands accept an optional [id] argument that defaults to $SLAYZONE_TASK_ID, which is automatically set in every task terminal. Commands that require a project (--project) default to $SLAYZONE_PROJECT_ID (also set automatically). All ID arguments support prefix matching — e.g. a1b2 matches a full UUID starting with a1b2.
Task lifecycle
slay tasks list [--project <name|id>] [--status <status>] [--done] [--limit <n>] [--json]— list tasks.--statusfilters by status key (resolved via the project's custom column config)--doneshows completed tasks across all projects using each project's column config; overrides--statusif both given- Default limit: 100
slay tasks create <title> [--project <name|id>] [--description <text>] [--status <status>] [--priority <1-5>] [--due <date>] [--template <name|id>] [--external-id <id>] [--external-provider <provider>]— create a task.--projectdefaults to$SLAYZONE_PROJECT_ID- If
--templateis omitted, the project's default template auto-applies (if one exists). Templates set terminal mode, initial status, priority, and provider config --external-idenables idempotent creation: if a task with the same(project, provider, external_id)exists, prints "Exists" and exits cleanly — useful for sync scripts- Reference artifacts in descriptions via
[title](artifact:<artifact-id>)
slay tasks view [id]— show task details including status, priority, description, tags, and subtasks.slay tasks update [id] [--title <title>] [--description <text>] [--append-description <text>] [--status <status>] [--priority <1-5>] [--due <date>] [--no-due] [--parent <id>] [--no-parent] [--permanent]— update a task.--append-descriptionadds text after a newline separator (mutually exclusive with--description)--no-dueclears the due date--parent <id>reparents under another task in the same project;--no-parentmakes it top-level--permanentconverts a temporary task to a real task
slay tasks progress <idOrValue> [value]— set task progress (integer 0-100).- Two-arg form:
slay tasks progress <id> <value> - One-arg form:
slay tasks progress <value>— id defaults to$SLAYZONE_TASK_ID
- Two-arg form:
slay tasks done [id] [--close]— mark task complete using the project's configured "done" status.--closealso closes the task tab in the app
slay tasks archive <id>— hide from kanban but keep in database.- Use for tasks you don't need visible but want to preserve
slay tasks delete <id>— permanently remove the task and all its data.slay tasks open [id] [--background]— focus the task in the SlayZone app window.--backgroundadds the tab without switching focus or stealing OS window focus (use for bulk-dispatch flows).slay tasks search <query> [--project <name|id>] [--limit <n>] [--json]— case-insensitive substring search across title and description.- Includes subtasks in results
- Results ordered by most recently updated
- Default limit: 50
Subtasks
slay tasks subtasks [id] [--json]— list subtasks of a task.slay tasks subtask-add <title> [--parent <id>] [--description <text>] [--status <status>] [--priority <1-5>] [--external-id <id>] [--external-provider <provider>]— add a subtask.--parentdefaults to$SLAYZONE_TASK_ID- Subtask inherits the parent's terminal mode
--external-iddeduplication works the same as task creation
Show full SKILL.md (358 more words)Show less
Blocking
Two independent blocking mechanisms: dependency-based blockers (task A blocks task B) and a standalone is_blocked flag with optional comment.
slay tasks blockers [id] [--add <ids...>] [--remove <ids...>] [--set <ids...>] [--clear] [--json]— view or modify dependency blockers — tasks that must be done before this one.- Without write flags, lists current blockers
- A task cannot block itself
slay tasks blocking [id] [--json]— list tasks that this task is blocking.slay tasks blocked [id] [--on] [--off] [--toggle] [--comment <text>] [--no-comment] [--json]— view or modify theis_blockedflag.--on/--off/--toggleset state--comment <text>sets blocked with a note (implies--on)--no-commentclears only the comment
Task tags
Tags are project-scoped — a tag name must exist in the project before it can be applied to a task.
slay tasks tag [taskId] [--json]— show current tags on a task.slay tasks tag [taskId] --set <name1> [name2...]— replace all tags with the given names.slay tasks tag [taskId] --add <name>— add a tag.- Idempotent — no error if already present
slay tasks tag [taskId] --remove <name>— remove a tag by name.slay tasks tag [taskId] --clear— remove all tags from the task.
Project tags
slay tags list [--project <name|id>] [--json]— list all tags in a project.--projectdefaults to$SLAYZONE_PROJECT_ID
slay tags create <name> [--project <name|id>] [--color <hex>] [--text-color <hex>]— create a new tag.--projectdefaults to$SLAYZONE_PROJECT_ID- Color defaults to #6366f1, text color to #ffffff
slay tags delete <id>— delete a tag.
Templates
Templates define defaults for new tasks: terminal mode, status, priority, provider config, panel visibility, and browser tabs.
slay templates list [--project <name|id>] [--json]— list templates.--projectdefaults to$SLAYZONE_PROJECT_ID- Shows which one is the project default
slay templates view <id> [--json]— view template details including all configured defaults.slay templates create <name> [--project <name|id>] [--terminal-mode <mode>] [--priority <1-5>] [--status <status>] [--default] [--description <text>]— create a template.--projectdefaults to$SLAYZONE_PROJECT_ID--defaultmakes it the project default, clearing any existing default (transactional)
slay templates update <id> [--name <n>] [--terminal-mode <m>] [--priority <1-5>] [--status <s>] [--default] [--no-default] [--description <text>]— update a template.--defaultclears all other defaults--no-defaultunsets only this template's default flag
slay templates delete <id>— delete a template.
© 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-tasks of debuglebowski/slayzone.
Open the folder on GitHubat commit e912716
Compare with similar skills
Slay Tasks 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 Tasks this skilldebuglebowski/slayzone | 191 | — | ~1.6k | Automated safety check: Pass | GPL-3.0 | |
| MemPalace Task HandoffMemPalace/mempalace | 59k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Planning And Task Breakdownabashev/vfs-s3 | 106 | 8 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Incremental Implementationaddyosmani/agent-skills | 102k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| ULW Plan Workflowcode-yeongyu/oh-my-openagent | 70k | — | ~3.9k | Automated safety check: Pass | Custom licence | |
| Implementation Plan Creatortailcallhq/forgecode | 7.6k | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Planning And Task Breakdown
abashev/vfs-s3
Breaks work into ordered tasks. An agent skill from abashev/vfs-s3.
Incremental Implementation
addyosmani/agent-skills
Delivers a change in thin vertical slices, each implemented, tested, verified and committed before the next, using vertical, contract-first or risk-first slicing.
ULW Plan Workflow
code-yeongyu/oh-my-openagent
Explore-first planning that turns a vague or large request into one decision-complete work plan, written only after your approval and executed by a separate worker.
Implementation Plan Creator
tailcallhq/forgecode
Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.
agtx One-Shot Project Runner
fynnfluegge/agtx
Runs a whole project unattended on an agtx kanban board, decomposing the goal, starting tasks, unblocking workers and merging each result.
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 Automations
debuglebowski/slayzone
Create and manage automations 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.
Related
Categories
Questions about Slay Tasks
What does Slay Tasks do?
Manage tasks, subtasks, tags, and templates via the slay CLI. Slay Tasks is an agent skill from debuglebowski/slayzone.
When should I use Slay Tasks?
Slay Tasks fits situations like: tasks that involve Task breakdown.
How do I install Slay Tasks in Claude Code?
Run `npx skills add debuglebowski/slayzone --skill slay-tasks -a claude-code`. Or copy the skill folder (.agents/skills/slay-tasks in debuglebowski/slayzone) into .claude/skills/slay-tasks in your project. Claude Code loads it when a task matches its description.
How do I install Slay Tasks in Codex?
Run `npx skills add debuglebowski/slayzone --skill slay-tasks -a codex`. Or copy the skill folder (.agents/skills/slay-tasks in debuglebowski/slayzone) into .agents/skills/slay-tasks in your project. Codex loads it when a task matches its description.
Can I use Slay Tasks 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-tasks -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-tasks, .gemini/skills/slay-tasks, .github/skills/slay-tasks and .opencode/skills/slay-tasks in your project.
What does Slay Tasks need to run?
SKILL.md names no scripts, command-line tools or credentials: Slay Tasks is instructions for the agent only.
Does Slay Tasks 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 Tasks 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 Tasks use?
Slay Tasks 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 Tasks use?
About 1.6k tokens (SKILL.md is roughly 6.4k 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 Tasks?
Skills that share tags, products or a category with Slay Tasks: MemPalace Task Handoff (MemPalace/mempalace, 59k stars), Planning And Task Breakdown (abashev/vfs-s3, 106 stars), Incremental Implementation (addyosmani/agent-skills, 102k stars) and ULW Plan Workflow (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Slay Tasks?
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.