discernment
Apply a structured judgment and discernment framework to any high-stakes decision, recommendation, or AI-generated output. Use this skill whenever the user wants to think more carefully before committing to something — a people decision, a strategic call, a piece of writing they're about to send, or an AI output they're not sure whether to trust. Trigger on phrases like "is this right?", "am I confident about this?", "help me think this through", "run the discernment framework", "judgment check", "calibration check", "am I being overconfident", "should I trust this output", "premortem", or any time someone is wrestling with whether their thinking is sound. Also trigger proactively when someone appears to be accepting a claim, recommendation, or AI-generated output without questioning it — especially on high-stakes topics like hiring, restructuring, or communications that will reach many people.
What this skill does
# Discernment Framework Good judgment is not about confidence. It is about calibration — knowing how much your confidence is warranted by the evidence, your actual expertise, and the quality of your thinking process. This framework draws on four bodies of work to help you assess that. Use this skill by understanding the situation first, defining the root problem using SCQuARE, then walking through the four lenses in order, and synthesising into a clear verdict with a specific next action. --- ## Step 0: Understand the situation Before applying any lens, establish: - **What exactly is being assessed?** A decision? A recommendation? A piece of AI-generated text? A course of action someone is about to commit to? - **What are the stakes?** Reversible or irreversible? Who is affected? What is the cost of being wrong? - **What has already been decided vs. what is still open?** This shapes whether the work is pre-decision quality-checking or post-decision review. Ask the user for this context if it isn't clear. Don't start the framework on thin air. --- ## Step 1: Root problem — SCQuARE Before applying any judgment lens, establish what problem is actually being solved. This step is easy to skip and almost always worth doing. It is based on the SCQuARE framework (Situation, Complication, Question, Answer, Rationale, Evidence), which forces crisp problem definition before analysis begins. The risk without this step: excellent thinking applied to the wrong question. Work through these five elements: - **Situation** — What is the stable, agreed-upon context? What do we know to be true and uncontroversial? (2–3 sentences max. If this is hard to state, the problem isn't well-formed yet.) - **Complication** — What has changed, or what tension exists, that makes the situation insufficient? This is the reason the decision or question has arisen at all. A good complication is specific — not "things are uncertain" but *what specifically* has created the need to act or decide. - **Question** — Given the situation and complication, what is the precise question that needs answering? This should be a single, crisp question. If there are multiple questions, the scope is too large — name the primary one. - **Answer** — What is the hypothesis or proposed answer to that question? This is what is about to be assessed, acted on, or committed to. Making it explicit is the whole point: you cannot pressure-test a vague intent. - **Rationale and Evidence** — Why do we believe this answer? What evidence supports it? And what evidence *against* it has been considered? If the rationale is thin, the rest of the discernment process will be doing more work. **The diagnostic question**: *Is the question we are actually trying to answer the right question — or is it a symptom of a deeper or different problem?* If the SCQuARE step surfaces a different root question than the one originally presented, name it explicitly and confirm with the user before proceeding. Applying the four lenses to the wrong question is a sophisticated way to get the wrong answer. --- ## The Four Lenses ### Lens 1 — Dunning-Kruger: Do you know what you don't know? The Dunning-Kruger effect is not just about being wrong. It is about lacking the metacognitive ability to recognise when you are wrong — which means the most dangerous moment is not when you know nothing, but when you know just enough to feel certain. Apply this lens by exploring: - **What is the person's actual depth of expertise in this specific domain?** Not adjacent experience — this domain. - **Is their confidence rising with familiarity, or with evidence?** Familiarity-driven confidence is a warning sign. - **Are there signals of "peak of Mount Stupid" thinking?** Easy answers, low uncertainty, dismissal of nuance. - **What would a genuine expert in this area say that this person has not considered?** The question to put to the user: *If you found out you were wrong about this, what would most likely be the reason?* If they struggle to answer that, the Dunning-Kruger risk is real. --- ### Lens 2 — Hogan Judgment: What is your decision-making style and where does it distort? Hogan's Judgment model identifies three personality dimensions that shape how people approach decisions — and each creates predictable blind spots under pressure: | Dimension | Poles | Blind spot risk | |---|---|---| | **Motivation** | Threat-avoidant ↔ Reward-seeking | Reward-seekers underweight downside risk. Threat-avoiders underweight opportunity. | | **Thinking style** | Tactical ↔ Strategic | Tactical thinkers over-optimise the immediate. Strategic thinkers lose the operational detail. | | **Information processing** | Intuitive ↔ Data-driven | Intuitive thinkers move fast on pattern-matching. Data-driven thinkers can stall or over-engineer. | Critically, Hogan adds a fourth dimension most models miss: **how a person responds to feedback after a decision goes wrong.** Leaders who cannot update on negative feedback repeat the same mistakes. Apply this lens by asking: - Which pole of each dimension does this person (or this reasoning) tend toward? - Given those tendencies, what is likely being underweighted in this decision? - If this decision turned out badly, what would they do with that information? Would they update, or explain it away? --- ### Lens 3 — Mark Egan / Behavioural Insights Team: Are you well-calibrated? Dr. Mark Egan's research at BIT shows that **overconfidence is the dominant bias** — 80%+ of UK adults are more confident than they are correct. The goal is not to become less confident; it is to become *well-calibrated*, meaning your confidence reliably tracks your accuracy. The BIT framework distinguishes three states: - **Overconfident**: confidence exceeds correctness — the most common and dangerous state - **Underconfident**: correctness exceeds confidence — often in experienced professionals with impostor syndrome - **Well-calibrated**: confidence and accuracy track each other — the goal Key debiasing tools from Egan's "good form for thinking" toolkit: **Premortem**: Before committing, imagine it is 12 months later and the decision has failed. What went wrong? This surfaces risks that forward-looking optimism hides. **Thinkgroup**: Deliberately include a dissenting voice before the decision is finalised. Not a devil's advocate for show — someone who genuinely sees it differently. **Confidence diagnostic**: Ask — on similar decisions in the past, how often was I right when I felt this certain? If you don't track that, your confidence numbers are noise. **"Cognitive hygiene" check**: Like eyesight, judgment degrades without regular calibration checks. Ask: when did I last get feedback that updated my thinking in this domain? Apply this lens by asking: - How confident is the person, on a scale of 0–100%? - What is their actual track record on similar judgments? - Has a premortem been run? Has a thinkgroup been consulted? - Is there evidence of "loud certainty" overriding calibrated thinking? --- ### Lens 4 — Tetlock / Superforecasting: Is the reasoning structured and updatable? Tetlock's research on superforecasters shows that well-calibrated judgment is learnable. Superforecasters are not smarter — they have better *process*. The key habits: **Outside view first**: Before reasoning from inside the specific situation, ask — what is the base rate? Of all similar decisions/situations/predictions, how often does it go this way? This counteracts the inside-view bias where our specific situation always seems exceptional. **Precise probabilities, not vague language**: "It's likely" is not a forecast. "I'd put this at 70%" is. Precision forces honesty and makes errors detectable. **What would change your mind?** A well-reasoned position has explicit conditions under which it would shift. If there is nothing that would change the person's view, it is not a belief — it is an identity. **Update proportionally to evide
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.