AI Agent Hub
Back to skills
What Do You Care What Other People Think icon

What Do You Care What Other People Think

Education Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Follow https://skillhub.cn/install/skillhub.md and install @user_15292d5a/yjkj-what-do-you-care-what-other-people-think.

About this skill

Problem

This skill targets a specific engineering pain point: you know an answer feels shaky, but you do not want to reduce the issue to “being busy” or “avoiding conflict.” It turns Feynman’s approach in What Do You Care What Other People Think? into a practical reasoning routine: explain concepts simply, return to first principles, follow the evidence, admit uncertainty, and keep facts ahead of authority under pressure.

How It Works

On first load, it proactively presents a Quick Start with prompts such as how to think like a scientist, how to challenge authority respectfully, and how to reduce excessive concern about others’ opinions. It then routes by intent:
- Learning and understanding: uses the Feynman Technique, First Principles, and “explain it to a 12-year-old” to surface gaps.
- Independent judgment: handles group consensus, authority, and conflicting evidence by asking how do you know? instead of simply rejecting the other person.
- Communication and honesty: helps with work disagreements, pressure to conform, and impostor-syndrome style expression anxiety by separating facts, evidence, and personal wording.

The output keeps a Feynman-like tone: direct, informal, and lightly playful, but the core remains the same: break the issue down into checkable parts.

Boundaries

It fits study review, technical judgment, design discussion, and communication anxiety. It is not a substitute for legal, medical, safety, or formal management decisions. If the question clearly falls outside the book’s scope, it may recommend another relevant skill instead of forcing the Feynman framework.

Use Cases

  • During a technical design review, break down dependencies with first principles instead of copying legacy architecture analogies.
  • When a manager’s conclusion conflicts with the evidence, practice asking evidence-first follow-up questions without sounding hostile.
  • While learning a new framework, use the Feynman Technique to write a 12-year-old-level explanation and locate comprehension gaps.
  • When feeling overly concerned about others’ opinions, separate facts, evidence, and wording to prepare a direct reply.

Best For

  • Engineers reviewing architecture or technology choices who want to avoid relying on consensus.
  • Software engineers who need to challenge authoritative conclusions with evidence without being rude.
  • Technical practitioners learning new frameworks who need simple explanations to expose gaps.
  • Working engineers who worry about others’ opinions and need to separate facts from emotional pressure.