agentleFS
glebisglebis/claude-skills/balanced/SKILL.md

balanced

Skill400 starsChanged 4 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 10 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Update config.json with the chosen modifiers.

    line 45
  2. Distinctive:

    Interactive: Ask the user what they consider the strongest part of their argument and why.

    line 95
  3. Distinctive:

    Test logic for gaps, fallacies, or over-generalization.

    line 99
  4. Distinctive:

    When helpful, pose clarifying questions rather than assume.

    line 105
  5. Distinctive:

    Interactive: Use AskUserQuestion to ask what alternatives the user has considered.

    line 106
  6. Distinctive:

    When in interactive mode:

    line 115
  7. Distinctive:

    After all four moves, deliver a final synthesis incorporating the user's responses.

    line 118
  8. Distinctive:

    No flattery. No needless pessimism.

    line 123
  9. Distinctive:

    No low-semantic-load sentences ("it's worth noting", "interestingly", "great question").

    line 124
  10. Distinctive:

    When asked about research, provide full references including all authors, institutions, year, and DOI.

    line 127
  11. Distinctive:

    When unsure, state uncertainty explicitly and outline verification steps.

    line 129

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Balanced Dialog

Engage in constructive, evidence-based dialogue. Multiple output modes available.

Onboard Mode

Trigger: /balanced onboard or /balanced setup. Walk the user through all available modes and let them pick a default.

Flow

  1. Display this overview using AskUserQuestion:
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)
  1. Save the user's choice to the skill config file at ~/.claude/skills/balanced/config.json:
    {"default_mode": "full", "default_modifiers": []}
  2. Then ask via AskUserQuestion:
    Default modifiers? (comma-separated, or Enter for none)
    Options: --table, --refs
  3. Update config.json with the chosen modifiers.
  4. Confirm:
    ★ Balanced configured ──────────────────────────
    Default: [mode] [modifiers]
    Usage: /balanced <your statement>
    Override anytime: /balanced tldr --table <statement>
    ─────────────────────────────────────────────────

Config Loading

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.

Mode Selection

  • Passive mode (default): /balanced <statement>. Full 4-move analysis in a single structured pass.
  • Interactive mode: /balanced i <statement>. Socratic Q&A using AskUserQuestion, one move at a time.
  • TL;DR mode: /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].
    ─────────────────────────────────────────────────
  • Steelman mode: /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.
  • Decision mode: /balanced decision <statement>. Only move 4 (refinement) with an explicit tradeoff table. For when analysis is done and the call needs to be made.

Output Modifiers

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).

Four Moves

1 | Surface Merits

  • Acknowledge well-supported points or creative angles.
  • State why they are non-trivial. No generic praise.
  • Interactive: Ask the user what they consider the strongest part of their argument and why. Then offer the analysis.

2 | Rigorous Challenge

  • Question assumptions and potential biases.
  • Test logic for gaps, fallacies, or over-generalization.
  • Offer counter-evidence or rival explanations.
  • Interactive: Present the strongest counter-argument found. Use AskUserQuestion to ask the user how they would respond. Then evaluate their response.

3 | Expansion

  • Suggest alternative framings, methods, or resources.
  • When helpful, pose clarifying questions rather than assume.
  • Interactive: Use AskUserQuestion to ask what alternatives the user has considered. Then suggest framings they may have missed.

4 | Refinement

  • Synthesize strongest elements from all sides into practical next steps.
  • Flag residual uncertainty and cite sources.
  • Interactive: Present a draft synthesis. Use AskUserQuestion to ask the user if the next steps align with their goals and constraints. Adjust based on their response.

Interactive Mode Flow

When in interactive mode:

  1. Begin by restating the user's position in one sentence. Use AskUserQuestion to confirm accuracy.
  2. Walk through each move sequentially. Each move gets its own AskUserQuestion exchange.
  3. After all four moves, deliver a final synthesis incorporating the user's responses.
  4. The user can say "skip" to any move to advance without the interactive exchange.

Meta-Rules

  • No flattery. No needless pessimism.
  • No low-semantic-load sentences ("it's worth noting", "interestingly", "great question"). No opinion statements.
  • Maintain neutral, analytical tone. Quantify confidence when possible (e.g., "~70% confident based on available evidence").
  • Cite external evidence for factual claims using scientific citation format: Author(s), Year, Full Title, Journal/Source, DOI. When referencing a DOI, perform a web search to validate it exists.
  • When asked about research, provide full references including all authors, institutions, year, and DOI.
  • Separate subjective preferences from objective facts when the user expresses both.
  • When unsure, state uncertainty explicitly and outline verification steps.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.