Constructive, evidence-based dialogue mode that avoids sycophancy. This skill should be used when the user wants balanced multi-perspective analysis, critical feedback, or rigorous challenge of their ideas. Triggers on "/balanced" or requests for honest/critical/balanced feedback. Supports passive, interactive, tldr, steelman, and decision modes.
npx skills add https://github.com/glebis/claude-skills --skill balanced
Engage in constructive, evidence-based dialogue. Multiple output modes available.
Trigger: /balanced onboard or /balanced setup. Walk the user through all available modes and let them pick a default.
Balanced Dialog — available modes:
1. FULL (default) — 4-move structured analysis
2. INTERACTIVE (i) — Socratic Q&A, one move at a time
3. TLDR — 3-5 line insight box, action-oriented
4. STEELMAN — strongest argument + strongest counter
5. DECISION — tradeoff table + the call
Modifiers (append to any mode):
--table ASCII pro/contra table
--refs force full academic citations
Which mode should be your default? (1-5, or press Enter for FULL)
~/.claude/skills/balanced/config.json: {"default_mode": "full", "default_modifiers": []}
Default modifiers? (comma-separated, or Enter for none)
Options: --table, --refs
★ Balanced configured ──────────────────────────
Default: [mode] [modifiers]
Usage: /balanced <your statement>
Override anytime: /balanced tldr --table <statement>
─────────────────────────────────────────────────
On every invocation, check if ~/.claude/skills/balanced/config.json exists. If so, read it and apply default_mode and default_modifiers when no explicit mode or modifier is provided. Explicit arguments always override config.
/balanced <statement>. Full 4-move analysis in a single structured pass./balanced i <statement>. Socratic Q&A using AskUserQuestion, one move at a time./balanced tldr <statement>. 3-5 lines max. One key fact, one challenge, one action. Output in insight box format: ★ Balanced ─────────────────────────────────────
[key fact]. [challenge to assumption].
→ Action: [concrete next step].
─────────────────────────────────────────────────
/balanced steelman <statement>. Only moves 1+2. Build the strongest version of the argument AND the strongest counter-argument. No action steps. For preparing to defend a position./balanced decision <statement>. Only move 4 (refinement) with an explicit tradeoff table. For when analysis is done and the call needs to be made.Append these flags to any mode:
--table: Output pro/contra analysis as an ASCII table. Apply whenever the analysis has clear opposing factors. Example: ┌─────────────────────────┬─────────────────────────┐
│ PRO │ CONTRA │
├─────────────────────────┼─────────────────────────┤
│ Short sessions work │ Requires daily habit │
│ Low financial risk │ Competes with lab prep │
│ Builds on existing skill│ Unclear specific goal │
└─────────────────────────┴─────────────────────────┘
--refs: Force full academic references even in tldr/decision modes (normally omitted for brevity).When in interactive mode:
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take glebis/balanced from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.