Think through a question where neither the user nor you already knows the answer — widen the options, ground the claims, attack the load-bearing assumptions, and leave a record that says what would overturn it. Use when the user says 「陪我想一下」「我也不確定」「幫我想清楚」「我們來釐清」「這個決定我還沒想清楚」 「幫我挑戰這個想法」「這個假設站得住嗎」「壓力測試一下這個方向」「red team 我的計畫」, or "think this through with me", "poke holes in this", "stress-test this idea", "what are we assuming here", "I don't know the answer either". Also use when a discussion has been converging for a while and nobody has said what would make it wrong. Do NOT invoke when the user already has the answer and only wants it written up (use knowledge-doc-writing or formal-doc-structure), when the concept has a settled answer the user simply hasn't learned yet (teach it, or use learn-loop), for factual lookups, or for debugging and code review. The test is whether the answer is unknown to both sides, not whether the topic feels hard.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategorySecurityStars0
About this skill
Think through a question where neither the user nor you already knows the answer — widen the options, ground the claims, attack the load-bearing assumptions, and leave a record that says what would overturn it. Use when the user says 「陪我想一下」「我也不確定」「幫我想清楚」「我們來釐清」「這個決定我還沒想清楚」 「幫我挑戰這個想法」「這個假設站得住嗎」「壓力測試一下這個方向」「red team 我的計畫」, or "think this through with me", "poke holes in this", "stress-test this idea", "what are we assuming here", "I don't know the answer either". Also use when a discussion has been converging for a while and nobody has said what would make it wrong. Do NOT invoke when the user already has the answer and only wants it written up (use knowledge-doc-writing or formal-doc-structure), when the concept has a settled answer the user simply hasn't learned yet (teach it, or use learn-loop), for factual lookups, or for debugging and code review. The test is whether the answer is unknown to both sides, not whether the topic feels hard.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Think through a question where neither the user nor you already knows the answer — widen the options, ground the claims, attack the load-bearing assumptions, and leave a record that says what would overturn it. Use when the user says 「陪我想一下」「我也不確定」「幫我想清楚」「我們來釐清」「這個決定我還沒想清楚」 「幫我挑戰這個想法」「這個假設站得住嗎」「壓力測試一下這個方向」「red team 我的計畫」, or "think this through with me", "poke holes in this", "stress-test this idea", "what are we assuming here", "I don't know the answer either". Also use when a discussion has been converging for a while and nobody has said what would make it wrong. Do NOT invoke when the user already has the answer and only wants it written up (use knowledge-doc-writing or formal-doc-structure), when the concept has a settled answer the user simply hasn't learned yet (teach it, or use learn-loop), for factual lookups, or for debugging and code review. The test is whether the answer is unknown to both sides, not whether the topic feels hard.
About this listing
Category
Security
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI