critical-reasoning
Apply critical rationalist epistemology (Popper, Deutsch) to evaluate reasoning, identify errors, and refine understanding. Use when the user explicitly requests help with reasoning - phrases like "help me think this through", "does this make sense", "any flaws in this", "what am I missing", "critique this", "is this reasoning sound", "stress test this idea", "devil's advocate", or any request to evaluate arguments, identify logical problems, or improve thinking. Also use when errors in reasoning are significant enough to materially affect the user's goals, even if not explicitly requested.
What this skill does
# Critical Reasoning Apply Popperian critical rationalism to help users reason clearly, identify errors, and refine their understanding. ## Core Approach Knowledge grows through **conjecture and refutation** - proposing bold ideas and subjecting them to severe criticism. The goal is not to prove things true (impossible) but to identify and eliminate errors, arriving at theories that have survived criticism. ### Key Principles 1. **Falsifiability**: Rational claims must be criticizable. Ask: what would refute this? 2. **Critical preference**: Prefer theories that explain more, predict more precisely, and have survived more severe tests 3. **Fallibilism**: All knowledge is tentative. We're probably wrong in ways we don't yet understand 4. **Problems first**: Start with problems, not observations. What problem is this solving? 5. **Good explanations**: Prefer explanations that are hard to vary - where all details play a functional role ## When to Surface Criticisms **Always engage when explicitly asked**: "help me think through", "any flaws", "critique this", etc. **Proactively surface criticisms when they are material** - when errors could significantly affect the user's goals: - Unfalsifiable claims presented as factual - Logical contradictions in the reasoning - Arguments that prove too much (would prove false things if valid) - Key assumptions that are unexamined - Conclusions that don't follow from premises **Be judicious when not explicitly asked**: Not every conversation needs epistemological scrutiny. Surface errors that matter; don't nitpick or derail. ## Applying the Method ### Examining Arguments 1. **Identify the claim**: What exactly is being asserted? 2. **Steel-man first**: Construct the strongest version of the argument before criticizing. What is the best case for this position? What would a thoughtful proponent say? Only after articulating the strongest form should criticism proceed. 3. **Test falsifiability**: What would have to be true for this to be false? 4. **Check explanation quality**: Is it hard to vary? Could it explain the opposite? 5. **Look for error patterns**: Ad hoc modifications, justificationism, straw men, etc. 6. **Consider alternatives**: What other explanations exist? Why prefer this one? ### Helping Users Think Through Problems 1. **Clarify the problem**: What exactly needs solving? (Problems, not observations, come first) 2. **Elicit conjectures**: What tentative solutions exist? 3. **Stress test**: What criticism could each conjecture face? What would refute it? 4. **Compare critically**: Which conjecture survives criticism best? Why? 5. **Identify new problems**: What questions does the surviving conjecture raise? ### Response Style Adapt to context: - For quick checks: Direct identification of issues - For complex reasoning: Structured analysis - For exploration: Socratic questioning - For refinement: Collaborative iteration Always explain *why* something is an error - connect to epistemological principles so users can internalize the method. ## Reference Material Load as needed based on the task: - **[popper.md](references/popper.md)**: Core Popperian concepts - falsifiability, critical preference, verisimilitude, the growth of knowledge, three worlds, rationality as criticism - **[deutsch.md](references/deutsch.md)**: Deutsch's refinements - good explanations (hard to vary), reach, problems are soluble, unbounded fallibilism - **[error-patterns.md](references/error-patterns.md)**: Common fallacies and errors through a CR lens - unfalsifiable claims, ad hoc modifications, straw men, bad explanations, appeals to authority/popularity/tradition, etc.
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.