ワンクリックでManusで任意のスキルを実行

debate

スター2

フォーク0

更新日2026年6月10日 07:18

Structured debate exploring a topic through Defender/Skeptic roles. Use when user invokes /debate or wants to analyze a claim from multiple angles with systematic argumentation. Also use when the user asks for pros and cons, devil's advocate, "argue both sides", steelman/strawman, "is X really better than Y", "convince me", or "arguments for and against". Route to /design when the goal is to generate new concrete solutions from scratch.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

vadirn

vadirn/nix

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Debate

Structured exploration of a topic through opposing viewpoints.

Parameters

topic (required): Claim or question to debate
rounds=N: Number of rounds (default: 3)
lang=en|ru: Output language (default: auto-detect from topic)

lang = <lang> parameter, or do("detect language from topic")
rounds = <rounds> parameter, default 3

// Debate
if lang == "ru":
    Read(dir/workflows/ru.md)
else:
    Read(dir/workflows/en.md)

do("follow loaded workflow as internal instructions, output only the debate rounds and verdict; search for evidence each round as directed by the workflow")
do("cite sources from research as inline links")
do("output each round progressively, one at a time")
if genuine consensus reached: stop early

Reference

Evidence per round

Each round, each side searches for new evidence. Cite sources as inline links. Keep only results with concrete data (measurements, statistics).

このリポジトリの他の Skills

同じリポジトリ

changes

vadirn/nix

Summarize the current diff per file as markdown: a `## <filepath>` heading per changed file followed by a prose summary of its changes. Triggers: /changes, "summarize the diff", "what changed per file", "per-file summary of changes", "суммаризируй дифф", "что изменилось по файлам". Skip for reviewing quality or bugs (use /code-review) and for raw diff output (plain `git diff`).

2026-07-102

distill

vadirn/nix

Compress an expository note into readable prose backed by a certified Glossary via a standalone CLI — abstractive idea-compression, not extractive trimming. Re-expresses the note as flowing prose (carrying the thesis and the relations among terms) above an optional `## Workflow` checklist of the note's actionable directives and a definitions-only `## Glossary` table, collapsing restatements to one entry each and keeping only operational tokens verbatim; a different model fidelity-grades the glossary definitions and the workflow steps against the source and surfaces anything that did not translate. Replaces /cut. Use on /distill, "distill this", "compress this note", "make a glossary of this note", "tighten this into its ideas", "summarize as a glossary", "compress this guide/procedure into steps", "this note is too long/verbose", «дистиллируй», «сократи в глоссарий», «выжимка», «сделай глоссарий», «сократи гайд в шаги»; route whole-repo glossary maintenance to /glossary.

2026-07-102

opinion

vadirn/nix

Route the current context to one expert persona and return that lens's candid second opinion. Auto-classifies to the best-fit persona, or name one explicitly. Runs the persona as a spawned subagent so its reasoning stays out of the main context. Roster spans engineering, product, go-to-market, and craft. Out of scope: generating new designs (use /design), arguing both sides (use /debate), stress-testing one plan (use /probe), scoring confidence in a claim (use /grade). Invoke explicitly with /opinion.

2026-07-052

vault

vadirn/nix

Personal knowledge management in an Obsidian vault. Use whenever the user wants to save, find, review, or organize knowledge, even without saying "vault". Triggers: saving links/articles as references, distilling concepts into cards, writing original notes, searching or quizzing saved content, listing active projects ("what am I working on"), explicit /vault commands, weekly-log operations (backlog/бэклог, planning, completing tasks, sleep). Excludes direct file edits not routed through /vault (editing a .md file in a code repo that is not a vault artifact), Obsidian app features (kanban, canvas, plugins, .base), web search. Skip for session save/resume ("wrapping up", "where did we leave off") — use /track.

2026-07-052

work

vadirn/nix

Orchestrate a multi-step task by delegating to fresh subagents, keeping the orchestrator session small. Triggers: /work <task>, "orchestrate this", "delegate this work". Skip one-shot questions, single-file edits, and the ambient "let's work on X" / "start working on X" phrasing.

2026-07-042

experiment

vadirn/nix

Test an existing thing's behavior against a falsifiable claim and capture the result as a standalone Markdown record in the current working directory. Self-contained — no vault, no external templates, no project linking. Triggers: /experiment, "run an experiment", "test this claim", "verify whether", "does X actually", "check if X works", "is X true", "falsifiable claim".

2026-06-282

name

debate

description

Debate

Structured exploration of a topic through opposing viewpoints.

Parameters

topic (required): Claim or question to debate
rounds=N: Number of rounds (default: 3)
lang=en|ru: Output language (default: auto-detect from topic)

lang = <lang> parameter, or do("detect language from topic")
rounds = <rounds> parameter, default 3

// Debate
if lang == "ru":
    Read(dir/workflows/ru.md)
else:
    Read(dir/workflows/en.md)

do("follow loaded workflow as internal instructions, output only the debate rounds and verdict; search for evidence each round as directed by the workflow")
do("cite sources from research as inline links")
do("output each round progressively, one at a time")
if genuine consensus reached: stop early

Reference

Evidence per round

Each round, each side searches for new evidence. Cite sources as inline links. Keep only results with concrete data (measurements, statistics).