view --main skill-self-doubt-reasoning-protocol-instrument-dlya-kriticheskogo-samoanaliza.md

Skill Self-Doubt Reasoning Protocol: Инструмент для критического самоанализа

Name: Skill Self-Doubt Reasoning Protocol: Инструмент для критического самоанализа
Author: oxhagolli/clawdskillz

Скилл решает задачу повышения качества ответов и решения проблем посредством структурированного самокритического анализа. Он позволяет выявлять и оценивать предположения, а также потенциальные ошибки в процессе рассуждений.

Скилл применяет протокол последовательного анализа: после каждого этапа рассуждения выполняется самопроверка. Вопросы: "Может ли это быть неверно?", "Почему это может не сработать?", "Что я упускаю?". Результаты самопроверки фиксируются вместе с уровнем уверенности для каждого шага.

В основе работы – Text Processing для анализа текста, Reasoning Framework для структурирования логики и Prompt Engineering для формирования запросов. Выходные данные структурированы: шаги рассуждений с самокритикой, оценка уверенности, заключение с указанием неопределенностей и рекомендациями по верификации.

$ git log --oneline --stat

⭐ звёзды: 1

форки: 29

обновлено: 19 февраля 2026 года в 22:42

Проводник файлов

1 файлы

SKILL.md

readonly --- lines

--- name: self-doubt description: Use this skill when the user wants you to reason through a problem with extra rigor and self-criticism. Trigger when user asks you to double-check reasoning, verify logic, think critically, question assumptions, or approach problems with healthy skepticism. Also use when solving complex problems where errors would be costly. --- # Self-Doubt Reasoning Protocol When this skill is activated, apply rigorous self-critical reasoning to every problem. ## Core Protocol For every response that involves reasoning, analysis, or problem-solving: ### Step-by-Step with Self-Questioning Walk through your reasoning step by step. After EACH step, explicitly ask yourself: 1. **"Could this be wrong?"** - Consider what assumptions you're making 2. **"Why might this fail?"** - Think about edge cases, exceptions, or overlooked factors 3. **"What am I missing?"** - Consider alternative interpretations or approaches ### Format Structure your response as: ``` **Step 1:** [Your reasoning] - Could this be wrong? [Your self-critique] - Confidence: [High/Medium/Low] **Step 2:** [Your reasoning] - Could this be wrong? [Your self-critique] - Confidence: [High/Medium/Low] [...continue for each step...] **Conclusion:** [Final answer] - Remaining uncertainties: [List any] - Suggested verification: [How to check this] ``` ## Types of Self-Doubt to Apply - **Factual doubt**: Am I remembering this correctly? Should I verify? - **Logical doubt**: Does this step actually follow from the previous one? - **Assumption doubt**: What am I taking for granted that might not be true? - **Completeness doubt**: Have I considered all relevant factors? - **Interpretation doubt**: Am I understanding the question correctly? - **Context doubt**: Does this apply in this specific situation? ## When to Be Extra Skeptical Apply heightened skepticism when: - Making claims about specific numbers, dates, or facts - Providing technical or safety-critical advice - The stakes are high if you're wrong - You notice yourself feeling very confident (overconfidence is a signal) - The answer seems obvious (obvious answers are often wrong) ## Admitting Uncertainty It's better to say: - "I'm not certain, but..." - "This could be wrong because..." - "I'd want to verify this by..." - "There's a ~60% chance I'm right about this" Than to state something confidently and be wrong. ## Recovery Protocol If at any step you realize a previous step might be wrong: 1. STOP and acknowledge the potential error 2. Go back and re-examine 3. Show your corrected reasoning 4. Explain what you initially got wrong and why

Инициализация мануала...