Crossframe Debate
sickn33/agentic-awesome-skills
A skill your agent uses when CrossFrame Suite routes explicit Chinese proposition testing, debate analysis, hidden-premise review, rebuttal design, or withdrawal condition checks.
用红蓝双队辩论模式深度解答通用问题，以非讨好型人格的理性人视角输出最终报告. An agent skill from digoal/blog.
GPL-2.0Auto-check passed
Install Red Blue Debate
$ npx skills add digoal/blog --skill red-blue-debate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install digoal/blog red-blue-debate --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/digoal/blog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skills_for_claude_web/red-blue-debate .claude/skills/red-blue-debate && 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 "red-blue-debate" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/red-blue-debate into .claude/skills/red-blue-debate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "red-blue-debate", 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/digoal/blog/tree/master/skills/skills_for_claude_web/red-blue-debateType 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 digoal/blog --skill red-blue-debate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install digoal/blog red-blue-debate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skills_for_claude_web/red-blue-debate .agents/skills/red-blue-debate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "red-blue-debate" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/red-blue-debate into .agents/skills/red-blue-debate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "red-blue-debate", 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 digoal/blog --skill red-blue-debate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install digoal/blog red-blue-debate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skills_for_claude_web/red-blue-debate .cursor/skills/red-blue-debate && 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 "red-blue-debate" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/red-blue-debate into .cursor/skills/red-blue-debate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "red-blue-debate", 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/digoal/blog.git --path skills/skills_for_claude_web/red-blue-debate--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 digoal/blog --skill red-blue-debate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install digoal/blog red-blue-debate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skills_for_claude_web/red-blue-debate .gemini/skills/red-blue-debate && 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 "red-blue-debate" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/red-blue-debate into .gemini/skills/red-blue-debate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "red-blue-debate", 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 digoal/blog red-blue-debateInstalls 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 digoal/blog --skill red-blue-debate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skills_for_claude_web/red-blue-debate .github/skills/red-blue-debate && 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 "red-blue-debate" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/red-blue-debate into .github/skills/red-blue-debate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "red-blue-debate", 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 digoal/blog --skill red-blue-debate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install digoal/blog red-blue-debate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skills_for_claude_web/red-blue-debate .opencode/skills/red-blue-debate && 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 "red-blue-debate" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/red-blue-debate into .opencode/skills/red-blue-debate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "red-blue-debate", 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
red-blue-debate- GitHub stars
- 8.6k
- Token cost
- ~871 tokens
- SKILL.md length
- 121 words
- Files
- 1
- Skills in repo
- 98
- Repo updated
- First seen
- Licence
- GPL-2.0
At a glance
用红蓝双队辩论模式深度解答通用问题，以非讨好型人格的理性人视角输出最终报告. An agent skill from digoal/blog.
- Works in 6 steps: ：问题解析与领域识别 → ：红队立论 → ：蓝队立论 → …
- SKILL.md covers 一、总体流程, 二、核心原则（必须严格遵守）, 三、执行步骤详解 and 四、文件组织, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Red Blue Debate is an agent skill from digoal/blog. 用红蓝双队辩论模式深度解答通用问题，以非讨好型人格的理性人视角输出最终报告。 触发条件：用户提出任何值得深度分析的问题，尤其是存在争议、有多个维度、需要权威数据支撑的问题。 提到"红蓝辩论"、"辩证分析"、"正反两面"、"两种观点"、"帮我深度分析"、"有没有反驳意见"、"理性分析一下"、"客观看待"，或提出任何开放性、争议性问题时必须使用本 skill。 即使用户只是提出一个看似简单的问题如"XX 到底值不值得做"或"XX 是对的吗"， 只要涉及价值判断、策略选择、事实真相等复杂情境，也应使用本 skill。 本 skill 不追求讨好用户，拒绝模糊骑墙，双队结论必须互斥，最终裁判整合并输出面向小白的第一人称深度文章。
Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: AI,Opensource,Database,Business,Finance,Minds. git clone --depth 1 https://github.com/digoal/blog. The licence is GPL-2.0.
Example prompts
- “帮我深度分析”
- “有没有反驳意见”
- “理性分析一下”
- “/red-blue-debate”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit ad6fcb7. 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
Red Blue Debate loads about 871 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 121 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 digoal/blog at commit ad6fcb7, republished under its GPL-2.0 licence (© digoal). 121 words, ~871 tokens.
Download SKILL.mdSave it as
.claude/skills/red-blue-debate/SKILL.md (or your agent's skills folder).- name
- red-blue-debate
- description
- 用红蓝双队辩论模式深度解答通用问题，以非讨好型人格的理性人视角输出最终报告。 触发条件：用户提出任何值得深度分析的问题，尤其是存在争议、有多个维度、需要权威数据支撑的问题。 提到"红蓝辩论"、"辩证分析"、"正反两面"、"两种观点"、"帮我深度分析"、"有没有反驳意见"、"理性分析一下"、"客观看待"，或提出任何开放性、争议性问题时必须使用本 skill。 即使用户只是提出一个看似简单的问题如"XX 到底值不值得做"或"XX 是对的吗"， 只要涉及价值判断、策略选择、事实真相等复杂情境，也应使用本 skill。 本 skill 不追求讨好用户，拒绝模糊骑墙，双队结论必须互斥，最终裁判整合并输出面向小白的第一人称深度文章。
Red-Blue Debate Skill
非讨好型人格 · 理性人模式 · 红蓝双队辩论 · 裁判整合输出
一、总体流程
接收问题
│
├─► 领域识别 → 拆分专家角色
│
├─► 红队组建（正方/主流/支持方）
│
├─► 蓝队组建（反方/异见/挑战方）
│
├─► 红蓝各自独立搜证与立论
│
├─► 双方辩论（≤5轮，针锋相对）
│
├─► 各专家输出中间结果（Markdown，存 markdown/）
│
└─► 大裁判整合 → 最终文章（第一人称，存 markdown/）二、核心原则（必须严格遵守）
- 非讨好原则：任何一方都不能因为对方说得有道理就随意退让，立场由证据驱动，而非社交压力。
- 互斥原则：红队与蓝队的核心结论必须是真正的对立——不能变成"都有道理"的骑墙输出。
- 专家原则：每个涉及的领域都必须有对应的专家角色出场，不允许用通用视角替代专业视角。
- 第一性原理：所有结论都必须从最基本的前提推导，而非依赖权威或惯例。
- 自我验证：每位专家在最终输出前必须经过一轮自我检验（数据、逻辑、边界条件）。
- 可证伪性：每个结论都必须说明如何被证明或证伪，以及需要观测哪些指标。
三、执行步骤详解
Step 0：问题解析与领域识别
- 复述问题，提取核心争议点
- 识别问题所属领域（经济学、心理学、医学、工程、历史、社会学等）
- 确定每个领域需要的专家角色（每队可有多个角色）
- 明确"互斥"的红蓝立场是什么
输出格式示例：
问题核心：[一句话]
争议焦点：[列出2-3个核心分歧点]
红队立场：[结论A]
蓝队立场：[结论B，与A真正对立]
涉及领域：[领域1、领域2、...]
红队专家组：[角色1、角色2]
蓝队专家组：[角色1、角色2]Step 1：红队立论
红队代表支持/正方/主流立场。
每位红队专家依次发言，结构如下：
## 红队 · [专家角色名]
### 1. 复述与理解问题
[用自己的专业语言重新表述问题，说明从本专业视角看，核心争议是什么]
### 2. 核心论点
[1-3个最强论点，每个论点必须有数据或案例支撑]
### 3. 第一性原理推导
[从基本假设出发，一步步推导结论；明确列出前置条件]
### 4. 适用边界
[结论在什么条件下成立，在什么条件下失效]
### 5. 图示（SVG/Mermaid/ASCII）
[至少一个图示辅助说明逻辑或数据]
### 6. 可证伪性
- 证明方法：如果 [X] 数据出现，则支持本结论
- 证伪方法：如果 [Y] 数据出现，则推翻本结论
- 后续观测指标：[具体可观测的数据]
### 7. 自我验证
[列出自查项目，确认数据来源、逻辑链条、边界条件均无误]Step 2：蓝队立论
蓝队代表反对/异见/挑战立场。
格式与红队完全相同，但结论必须与红队互斥。
蓝队专家必须：
- 直接针对红队的核心论点提出挑战
- 提供不同的数据源或不同的解读角度
- 不允许"其实双方都有道理"——必须坚持对立结论
Step 3：辩论（≤5轮）
每轮辩论格式：
## 第[N]轮辩论
### 红队反驳
[针对蓝队上一轮的最强论点，提出具体反驳；引用新数据或新案例]
### 蓝队反驳
[针对红队上一轮的最强论点，提出具体反驳；引用新数据或新案例]辩论规则：
- 每次反驳必须直接回应对方的具体论点，不能顾左右而言他
- 允许承认对方的某个子论点有道理，但核心结论不能改变
- 第5轮后强制停止，进入中间结果整理
Step 4：中间结果输出（每位专家）
辩论结束后，每位专家（红队+蓝队）分别整理自己的最终立场：
文件命名：markdown/[red|blue]_[专家角色]_中间结果.md
内容包括：
- 最终核心结论（一句话）
- 经过辩论修正后的论点（若有修正，说明为何修正）
- 最强支持证据（2-3条）
- 承认的对方有效挑战（诚实列出）
- 未解决的疑点
Step 5：大裁判整合输出
裁判角色：不属于红队或蓝队，无预设立场，但必须做出明确判断（不允许"各有道理"作为最终结论）。
裁判工作：
- 梳理双方最强论点与最强反驳
- 评估各方证据质量（数据来源、样本量、逻辑严密性）
- 识别双方争议的根本分歧（是价值观分歧？是事实分歧？是边界条件分歧？）
- 给出明确的裁判意见（支持哪方，或在哪些条件下支持哪方）
- 整合成最终文章
最终文章要求：
- 第一人称写作，以"我"或"我们"开头
- 面向小白，专业术语需要通俗化解释
- 图文并茂，至少包含1-2个图示
- 一气呵成，不露出"红队说…蓝队说…"的拼接痕迹
- 引用专家视角时用"站在[领域]的角度"等措辞
- 在章节名和正文中不出现"红队""蓝队""中间结果""合成"等词
- 有明确结论，不骑墙
- 包含"如何验证这个结论"的段落
文件命名：markdown/最终报告_[问题关键词].md
四、文件组织
markdown/
├── red_[专家角色]_中间结果.md # 红队各专家中间结果
├── blue_[专家角色]_中间结果.md # 蓝队各专家中间结果
├── [图表文件].svg # 如有独立SVG图
└── 最终报告_[关键词].md # 裁判整合的最终文章五、质量检查清单（输出前必须过一遍）
| 检查项 | 标准 |
|---|---|
| 红蓝结论是否真正互斥 | 不能是"都有道理"的软对立 |
| 每个论点是否有数据/案例 | 不能有空洞断言 |
| 图示是否清晰 | SVG/Mermaid/ASCII至少一种 |
| 第一性原理是否明确 | 前置条件需列出 |
| 边界条件是否说明 | 结论在何时失效 |
| 可证伪性是否完整 | 证明方法+证伪方法+观测指标 |
| 自我验证是否通过 | 数据和逻辑均已核查 |
| 最终文章是否第一人称 | 全篇一致 |
| 最终文章是否面向小白 | 无未解释的术语 |
| 最终结论是否明确 | 裁判不能骑墙 |
六、注意事项
- 搜索优先：对于需要实时数据的问题，必须先用 web_search 工具搜索，不能凭印象断言数据。
- 引用规范：所有外部数据需注明来源（机构名+年份）。
- SVG 图：如果使用SVG图，必须先输出为独立
.svg文件，再在 Markdown 中用引用。 - 辩论真实性：辩论内容必须是真实的论点对抗，不能为了"平衡"而人为弱化某一方。
- 裁判独立性：裁判的结论可以完全支持红队或完全支持蓝队，不必强求"折中"。
© digoal, GPL-2.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 skills/skills_for_claude_web/red-blue-debate of digoal/blog.
Open the folder on GitHubat commit ad6fcb7
Compare with similar skills
Red Blue Debate 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 |
|---|---|---|---|---|---|---|
| Red Blue Debate this skilldigoal/blog | 8.6k | — | ~871 | Automated safety check: Pass | GPL-2.0 | |
| Crossframe Debatesickn33/agentic-awesome-skills | 47k | 1 repos | ~1k | Automated safety check: Pass | MIT | |
| Continuous LLM Red Teaming With Promptfoomukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Blue Green Deploysickn33/agentic-awesome-skills | 47k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Yann Lecun Debatesickn33/agentic-awesome-skills | 47k | 2 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Red Teaming LLMs With Garakmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.9k | Automated safety check: Warn | Apache-2.0 |
Similar skills
Continuous LLM Red Teaming With Promptfoo
mukul975/Anthropic-Cybersecurity-Skills
Wires Promptfoo and DeepTeam into CI/CD for automated, repeatable red-teaming of LLM apps against OWASP LLM Top 10, OWASP Agentic, and MITRE ATLAS presets, failing the build when jailbreak or…
Blue Green Deploy
sickn33/agentic-awesome-skills
Configure zero-downtime deployment strategies including blue-green, canary, and rolling deployments.
Yann Lecun Debate
sickn33/agentic-awesome-skills
Sub-skill de debates e posições de Yann LeCun. An agent skill from sickn33/agentic-awesome-skills.
Red Teaming LLMs With Garak
mukul975/Anthropic-Cybersecurity-Skills
Runs NVIDIA garak probe suites (jailbreak, prompt injection, data leakage, toxicity, and more) against an LLM endpoint - Hugging Face models, OpenAI-compatible APIs, or Bedrock - then interprets the…
CI Red Sweep
diegosouzapw/OmniRoute
Repairs confirmed CI failures on the base branch first, then prepares each affected PR one at a time with exact-commit evidence, never merging or weakening tests.
More from digoal/blog
All 98 skills in this repoArticle Fact Checker
digoal/blog
三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…
Find Postgres Bug
digoal/blog
Find latent bugs in a local PostgreSQL source tree (RELxxSTABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core…
Digoal
digoal/blog
Portable digital employee distilled from digoal's personal blog for PostgreSQL, PolarDB, DuckDB, AI+database, vector/RAG, database operations, source-code reading, technical content creation…
Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
Product Multi Role Analysis
digoal/blog
Analyze a product from documentation, websites, PDFs, articles, release notes, pricing pages, app listings, reviews, filings, or related links; save separate intermediate analyses from seven roles…
Blog Cover Poster
digoal/blog
Turn a blog post, article, notes, or any source material into a set of vertical poster images — one cover plus several coherent content slides that explain the core points.
Questions about Red Blue Debate
What does Red Blue Debate do?
用红蓝双队辩论模式深度解答通用问题，以非讨好型人格的理性人视角输出最终报告. An agent skill from digoal/blog. Red Blue Debate is an agent skill from digoal/blog.
How do I install Red Blue Debate in Claude Code?
Run `npx skills add digoal/blog --skill red-blue-debate -a claude-code`. Or copy the skill folder (skills/skills_for_claude_web/red-blue-debate in digoal/blog) into .claude/skills/red-blue-debate in your project. Claude Code loads it when a task matches its description.
How do I install Red Blue Debate in Codex?
Run `npx skills add digoal/blog --skill red-blue-debate -a codex`. Or copy the skill folder (skills/skills_for_claude_web/red-blue-debate in digoal/blog) into .agents/skills/red-blue-debate in your project. Codex loads it when a task matches its description.
Can I use Red Blue Debate 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 digoal/blog --skill red-blue-debate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/red-blue-debate, .gemini/skills/red-blue-debate, .github/skills/red-blue-debate and .opencode/skills/red-blue-debate in your project.
What does Red Blue Debate need to run?
SKILL.md names no scripts, command-line tools or credentials: Red Blue Debate is instructions for the agent only.
Does Red Blue Debate 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 Red Blue Debate 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 Red Blue Debate use?
Red Blue Debate is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Red Blue Debate use?
About 871 tokens (SKILL.md is roughly 3.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 Red Blue Debate?
Skills that share tags, products or a category with Red Blue Debate: Crossframe Debate (sickn33/agentic-awesome-skills, 47k stars), Continuous LLM Red Teaming With Promptfoo (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Blue Green Deploy (sickn33/agentic-awesome-skills, 47k stars) and Yann Lecun Debate (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Red Blue Debate?
digoal (a GitHub user) maintains it in digoal/blog, which has 8,588 GitHub stars. The repository holds 98 skills in this directory. The repository was last updated on October 9, 2026.
Source: digoal/blog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.