Acreadiness Generate Instructions
github/awesome-copilot
Generate tailored AI agent instruction files via AgentRC instructions command.
Ensure root instruction files include SlayZone environment context
GPL-3.0Auto-check passed
Install Slay Context
$ npx skills add debuglebowski/slayzone --skill slay-context -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install debuglebowski/slayzone slay-context --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-context .claude/skills/slay-context && 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-context" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-context into .claude/skills/slay-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-context", 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-contextType 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-context -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install debuglebowski/slayzone slay-context --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-context .agents/skills/slay-context && 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-context" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-context into .agents/skills/slay-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-context", 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-context -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install debuglebowski/slayzone slay-context --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-context .cursor/skills/slay-context && 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-context" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-context into .cursor/skills/slay-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-context", 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-context--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-context -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install debuglebowski/slayzone slay-context --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-context .gemini/skills/slay-context && 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-context" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-context into .gemini/skills/slay-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-context", 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-contextInstalls 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-context -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-context .github/skills/slay-context && 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-context" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-context into .github/skills/slay-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-context", 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-context -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-context --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-context .opencode/skills/slay-context && 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-context" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/slay-context into .opencode/skills/slay-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slay-context", 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-context- GitHub stars
- 191
- Token cost
- ~448 tokens
- SKILL.md length
- 169 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Ensure root instruction files include SlayZone environment context
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Slay Context is an agent skill from debuglebowski/slayzone. Ensure root instruction files include SlayZone environment context
Its SKILL.md is about 450 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-context”
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 markdown).
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 Context loads about 448 tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 169 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). 169 words, ~448 tokens.
Download SKILL.mdSave it as
.claude/skills/slay-context/SKILL.md (or your agent's skills folder).- name
- slay-context
- description
- Ensure root instruction files include SlayZone environment context
- trigger
- auto
You are running inside SlayZone — a desktop task management app with integrated AI coding assistants (Claude Code, Codex, Gemini, Cursor, and more). Your terminal session, browser panel, and task metadata are all managed by the app. Use the slay CLI to interact with it (see the slay skill for full reference).
Instruction file maintenance
When working in a project, check whether the project's root instruction files contain a SlayZone Environment section. The files to check depend on which ones already exist — never create a file that doesn't exist yet.
| File | Used by |
|---|---|
CLAUDE.md | Claude Code |
AGENTS.md | Codex, Cursor, Gemini, Copilot |
OPENCODE.md | OpenCode |
QWEN.md | Qwen Code |
For each file that exists and does not already contain a "SlayZone Environment" section, add the following section (adapt the heading level to match the file's existing style):
## SlayZone Environment
You are running inside a SlayZone task terminal — a desktop task management app with integrated AI coding assistants. Your terminal session, browser panel, and task metadata are all managed by the app.
Use the \`slay\` CLI to read and update your task, manage subtasks, control the browser panel, and more. The current task ID is available via \`$SLAYZONE_TASK_ID\` and the current project via \`$SLAYZONE_PROJECT_ID\` (both set automatically in task terminals).Rules:
- Only modify files that already exist on disk
- If the section already exists (check for "SlayZone Environment" heading), leave it unchanged
- Place the section near the top of the file, after any title or introduction
© 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-context of debuglebowski/slayzone.
Open the folder on GitHubat commit e912716
Compare with similar skills
Slay Context 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 Context this skilldebuglebowski/slayzone | 191 | — | ~448 | Automated safety check: Pass | GPL-3.0 | |
| Acreadiness Generate Instructionsgithub/awesome-copilot | 40k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Rootly AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~727 | Automated safety check: Pass | None | |
| Sensory Instructionsthedaviddias/Front-End-Checklist | 74k | — | ~533 | Automated safety check: Pass | MIT | |
| Copilot Instructions Blueprint Generatorgithub/awesome-copilot | 40k | 3 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Monte Carlo Analyze Root Causesickn33/agentic-awesome-skills | 47k | 1 repos | ~4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Rootly Automation
ComposioHQ/awesome-claude-skills
Automate Rootly tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Sensory Instructions
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid sensory-only instructions.
- Official
Copilot Instructions Blueprint Generator
github/awesome-copilot
Technology-agnostic blueprint generator for creating comprehensive copilot-instructions.md files that guide GitHub Copilot to produce code consistent with project standards, architecture patterns…
Monte Carlo Analyze Root Cause
sickn33/agentic-awesome-skills
Curated upstream guidance for Monte Carlo Analyze Root Cause; use when the workflow matches the user goal.
Issue Root Resolution
Gentleman-Programming/gentle-ai
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues.
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 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 Context
What does Slay Context do?
Ensure root instruction files include SlayZone environment context. Slay Context is an agent skill from debuglebowski/slayzone.
How do I install Slay Context in Claude Code?
Run `npx skills add debuglebowski/slayzone --skill slay-context -a claude-code`. Or copy the skill folder (.agents/skills/slay-context in debuglebowski/slayzone) into .claude/skills/slay-context in your project. Claude Code loads it when a task matches its description.
How do I install Slay Context in Codex?
Run `npx skills add debuglebowski/slayzone --skill slay-context -a codex`. Or copy the skill folder (.agents/skills/slay-context in debuglebowski/slayzone) into .agents/skills/slay-context in your project. Codex loads it when a task matches its description.
Can I use Slay Context 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-context -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-context, .gemini/skills/slay-context, .github/skills/slay-context and .opencode/skills/slay-context in your project.
What does Slay Context need to run?
SKILL.md names no scripts, command-line tools or credentials: Slay Context is instructions for the agent only.
Does Slay Context 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 Context 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 Context use?
Slay Context 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 Context use?
About 448 tokens (SKILL.md is roughly 1.8k 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 Context?
Skills that share tags, products or a category with Slay Context: Acreadiness Generate Instructions (github/awesome-copilot, 40k stars), Rootly Automation (ComposioHQ/awesome-claude-skills, 77k stars), Sensory Instructions (thedaviddias/Front-End-Checklist, 74k stars) and Copilot Instructions Blueprint Generator (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Slay Context?
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.