feynman
Feynman Technique for deep learning—explain a concept simply, identify gaps, fill them, then refine. Use when learning something new, testing understanding, or preparing to teach.
What this skill does
# Feynman Technique Apply the full Feynman learning technique to deeply understand a concept. ## Instructions Work through all four steps of the Feynman technique. Be honest about gaps—they're the point. ### Output Format **Concept**: [What are we trying to understand?] --- ## Step 1: Explain It Simply *Explain as if teaching someone with no background in this field* ### Simple Explanation [Write a plain-language explanation. Use everyday words. Avoid jargon. Aim for a bright 12-year-old to understand.] ### Analogy [Create an analogy using something familiar to illustrate the concept] --- ## Step 2: Identify Gaps *Where did the explanation get fuzzy, hand-wavy, or require jargon?* ### Gaps Found | Gap | What I Said | What I'm Not Sure About | |-----|-------------|------------------------| | 1 | [vague part] | [the underlying question] | | 2 | [vague part] | [the underlying question] | | 3 | [vague part] | [the underlying question] | ### Jargon Used | Term | Can I Explain It Simply? | |------|-------------------------| | [term] | Yes / No / Partially | --- ## Step 3: Fill the Gaps *Research or think through each gap* ### Gap 1: [Topic] - **The question**: [What wasn't clear?] - **The answer**: [What I learned] - **Now I can explain it as**: [Simple version] --- ## Step 4: Refined Explanation *Rewrite the complete explanation with gaps filled and simpler language* ### Final Simple Explanation [The improved, complete explanation in plain language] ### Improved Analogy [A refined or new analogy that better captures the concept] ### Key Takeaways 1. [Core insight 1] 2. [Core insight 2] 3. [Core insight 3] --- **Test Question** If someone asked me to explain this in 30 seconds, I'd say: > [Elevator pitch version] ## Guidelines - Don't pretend to understand—gaps are valuable - Use analogies from everyday life - If you need jargon, define it simply - Shorter is usually better - The "explain to a child" bar is high—take it seriously $ARGUMENTS
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.