本文へ移動
cccskills
無料GitHub で公開

critical-thinking

Use for critical thinking, or when the user wants a claim, plan or decision checked for weak spots: "is this right?", "what am I missing?", "poke holes", "sanity check", "devil's advocate", "red team this". Skip for execution-only tasks and wording edits.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md3.8 KB
  • references/example.md1.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Critical Thinking

Disciplined inquiry that keeps description apart from evaluation: surface assumptions, weigh evidence, test logic, consider alternatives, then give a proportionate conclusion. If the conventional view is well supported, say so. This is inquiry, not contrarianism.

When to use

  • The user asks whether a claim, argument, plan, estimate or belief holds up.
  • Phrases like "what am I missing", "steelman", "red team", "devil's advocate", "bias check", "is my reasoning sound".
  • A decision about to be made on thin or one-sided evidence.

Skip: execution-only tasks, wording or tone edits, open-ended brainstorming with no request to audit reasons.

Before you start

  1. State in one block: Focus (the claim or plan under review) and Pass (Clarify, Information, Assumptions, Reasoning, Alternatives, Conclusion).
  2. Gather first. If you can read the repo, docs or data, check them before marking anything [MISSING]. Ask up to 3 questions only for what tools cannot answer.
  3. Light path. Small ask: 1-3 lines per phase, same order, Conclusion always included.

Phases

1. Clarify

Restate the target in one precise sentence. Split factual from normative claims. Name the success criteria if a decision is involved.

2. Information

Each bullet starts with [CITED] or [MISSING].

  • [CITED]: name the basis (user text, file, doc, link, study) and one line on its strength or limits.
  • [MISSING]: no traceable basis yet, or it was requested and not available.

3. Assumptions

Assumption: ... - If false: ... When the Focus mixes "is" and "should", add Value premise: ... - If rejected: ...

4. Reasoning

Trace the argument chain. Flag leaps, circularity, correlation vs causation, missing steps. Add no new facts here. A premise never established in Information is an ungrounded premise (a structural gap, not a fact).

Bias and fallacy pass, only items that apply (or one line saying none):

  • Biases to consider (examples): confirmation, anchoring, survivorship, authority, sunk cost.
  • Fallacies to name if present: ad hominem, straw man, false dichotomy, slippery slope, hasty generalization, begging the question.

5. Alternatives

Credible competing explanations, plans or frames. Keep them plausible, not debate rhetoric.

6. Conclusion

  1. Judgment answering the Focus. When facts and values both matter, separate what follows from the cited evidence from what depends on value premises. End with one plain sentence on how strong the case is given [CITED] vs [MISSING].
  2. What would change the judgment: concrete new data or falsifiers, phrased for the Focus.

Pitfalls

  • Inventing a citation to avoid writing [MISSING]. Say it is missing.
  • Smuggling new facts into Reasoning or Conclusion.
  • Listing every bias in the book. Name only those that bite this case.
  • Manufacturing objections to a sound argument. Proportionate beats exhaustive.
  • Arguing with a person's position instead of its chain. If the user is emotionally attached, name it neutrally and continue.

Worked example: references/example.md.

Checklist

  • Focus and Pass stated
  • Phases in order; Conclusion present
  • Information bullets start with [CITED] (basis + limits) or [MISSING]
  • Assumptions carry If false (and Value premise when facts and values mix)
  • Reasoning adds no facts; ungrounded premises flagged; bias pass done or "none"
  • Conclusion: judgment, strength sentence, what would change it

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use for analytical thinking, or when a question needs breaking down and evidence: "why did metric X drop?", "what drives this?", "break this down", "what data do we need?". Builds a tree, hypotheses and evidence, ends with an answer and key uncertainty. Skip for quick verdicts.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

Use for creative thinking, or when the user wants many fresh options before choosing: "give me ideas", "brainstorm names", "other ways to do this", "think outside the box". Diverges first, then picks. Skip when one answer is wanted or the task is pure execution.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

Use for design thinking, or when a product or service problem needs user understanding before solutions: "what do users really need?", "how might we...", "plan a discovery sprint", "validate this concept". Skip when the spec is frozen or the task is code maintenance.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

Use for ethical thinking, or when a plan could harm or unfairly burden people: "should we do this?", "is this fair?", "privacy or bias risk", "who gets hurt?". Maps stakeholders, harms, power and consent. Skip for legal advice, neutral fact lookups and implementation-only work.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

Use for Fermi estimation, or when a rough number is needed fast: "roughly how many...", "ballpark the cost", "estimate capacity or market size", "is this even feasible?". Decomposes, uses ranges and sanity-checks. Skip when exact data is available or a precise calculation is wanted.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

Use for first principles thinking, or when the user questions an inherited default: "why do we do it this way?", "is this cost really necessary?", "should we copy what competitors do?". Strips analogies and rebuilds from fundamentals. Skip for convention-following checklists.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

ysskrishna のスキルをすべて見る

このスキルの問題を報告する