paper-to-intuition
Transforms an academic paper into deep, multi-layered understanding. Use when asked to explain a paper, break down a research paper, understand an arXiv paper, or build intuition for a technical concept from a paper. Generates explanations at multiple levels plus visual intuition diagrams.
What this skill does
# Paper to Intuition
Transform dense academic papers into genuine understanding through layered explanation and visual intuition.
## Process
1. **Get the paper** - Ask for the arXiv link, PDF, or paper title
2. **Extract the core** - Identify the single key insight (one sentence)
3. **Build the ladder** - Create explanations at 4 levels
4. **Visualize intuition** - Generate interactive diagrams
5. **Stress test understanding** - "What breaks if we remove X?"
## The Explanation Ladder
Generate explanations at each level, with each building on the last:
### Level 1: ELI5 (1 paragraph)
- No jargon, no equations
- Use familiar analogies from everyday life
- A curious 10-year-old should roughly get it
### Level 2: Undergraduate (2-3 paragraphs)
- Assume calculus, basic linear algebra, intro ML
- Introduce key terms with definitions
- Connect to textbook concepts they'd know
### Level 3: Graduate (3-4 paragraphs)
- Assume ML fundamentals, optimization, probability
- Discuss relationship to prior work
- Explain why naive approaches don't work
- Cover the key equations with plain-English annotations
### Level 4: Researcher (2-3 paragraphs)
- Assume field expertise
- Subtle technical contributions
- Limitations and open questions
- How this changes what's possible
## Key Equations Breakdown
For each important equation:
```
[Equation in LaTeX]
In words: [Plain English translation]
Each term:
- [symbol]: [what it represents] [why it's there]
Intuition: [Why this mathematical form? What would change if we used a different form?]
```
## Visual Intuition Artifact
Generate a self-contained HTML file with:
- **Architecture diagram** - Boxes and arrows showing information flow
- **Interactive sliders** - Manipulate key parameters, see effects
- **Before/after comparisons** - What the method improves over baselines
- **Failure case visualization** - When and why it breaks down
Use SVG for diagrams, vanilla JavaScript for interactivity. Dark theme, clean typography.
```html
<!DOCTYPE html>
<html>
<head>
<title>[Paper Name] - Visual Intuition</title>
<style>
:root { --bg: #1a1a2e; --text: #eee; --accent: #4f8cff; }
/* Clean, research-aesthetic styling */
</style>
</head>
<body>
<h1>[Paper Title]</h1>
<p class="tldr">[One-sentence insight]</p>
<section id="architecture">
<svg><!-- Information flow diagram --></svg>
</section>
<section id="interactive">
<!-- Parameter sliders with live updates -->
</section>
<section id="comparisons">
<!-- Before/after, ablations -->
</section>
</body>
</html>
```
## The "What Breaks?" Analysis
For each major component, explain:
1. **What it does** - The role this component plays
2. **What breaks without it** - Concrete failure mode
3. **Why this solution** - Alternatives considered, why this won
4. **The tradeoff** - What we pay for this choice (compute, complexity, assumptions)
## Output Structure
Deliver as a structured document:
```markdown
# [Paper Title]
**TL;DR:** [One sentence]
**Why it matters:** [One paragraph on significance]
## The Explanation Ladder
### ELI5
[...]
### Undergraduate Level
[...]
### Graduate Level
[...]
### Researcher Level
[...]
## Key Equations
### Equation 1: [Name]
[Breakdown as specified above]
## What Breaks If We Remove...
### [Component 1]
[Analysis]
### [Component 2]
[Analysis]
## Visual Intuition
[Link to or embed HTML artifact]
## Further Reading
- [Prerequisite paper 1]
- [Follow-up work 1]
```
## Quality Standards
- Every analogy must be accurate, not just catchy
- Equations must be explained, not just translated
- Visuals must reveal structure, not just decorate
- The researcher-level section should contain insight, not just summary
- Admit when something is genuinely confusing or poorly explained in the original paper
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.