Use this skill when the user points out a concept in a paper note and asks to explain it as a standalone Obsidian note. Triggers on phrases like "explain this concept", "what is X", "create a concept note for X".
When the user identifies a concept from a paper note, create a standalone explanation note and link it back.
PhD-Research/Papers/OpenVlaOft.md)Read the source paper note to understand how the concept is used in context.
Research the concept: Use web search or fetch the original paper/resource to get an accurate, thorough understanding of the concept.
Read an existing concept note from PhD-Research/Concepts/ for style and structure reference.
Derive the filename from the concept name using PascalCase with hyphens between words (e.g., , ).
FiLM-Conditioning.mdMLP-MaxPool-PointCloud-Encoder.mdWrite the concept note to PhD-Research/Concepts/<filename>.md following this structure:
---
title: "<Concept Name>"
tags:
- concept
- <relevant-domain-tags>
aliases:
- <common alternative names>
---
# <Concept Name>
> [!abstract] One-line summary
> <One clear sentence explaining what this concept does.>
## The Problem It Solves
<What gap or challenge does this concept address?>
## How It Works (Step by Step)
<Clear explanation with diagrams/code blocks if helpful. Use math notation where appropriate.>
## In Practice
<Concrete usage details, parameter values, or implementation notes.>
## Related
- [[<Related concepts and papers>]]
Adapt sections as needed — not every concept needs all sections. Add sections like "Why It Works", "Trade-offs", or "Analogy" when they help understanding.
Link the concept in the source paper note: If a source paper note was provided, add a [[ConceptName]] wikilink in the relevant location within that paper note (typically where the concept is mentioned or in the Connections section). Only add the link if it doesn't already exist.
Apply the obsidian:obsidian-markdown skill when writing the note.