Loading...
Loading...
Found 13 Skills
Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?"
Discover cross-domain connections across the wiki. Use when the user wants to find analogies, tensions, or surprising links between concepts from different fields, says "explore", "find connections", "what connects", or wants to discover patterns across their wiki, second brain, or knowledge base.
Research on Historical Isomorphism and Standard Answers. Abstract the complex dilemma the user is facing into a structural fingerprint, search for truly isomorphic successful cases, failed cases, and counterexamples in business history, management history, technology history, career history, and institutional history. Compare the constraints, decisions, and outcomes of the parties involved, and extract recurring solutions, applicable conditions, and failure boundaries. Trigger methods: /dbs-standard-answer, /标准答案 (Standard Answer), "Who faced similar problems in history?", "Has anyone encountered this situation before?", "How did they resolve it back then?", "Is there a classic solution to this problem?", "First help me find historical analogies?", "What was the standard answer in the past?". Find structurally analogous historical cases and evidence-backed standard answers. Use when the user wants to situate a current dilemma in history, compare how others addressed it, and extract recurring mechanisms with conditions and limits.
Use historical analogies to inform strategic decisions by identifying structural similarities and differences between past and present situations. Use this skill when the user draws on historical precedent to justify a strategy, needs to evaluate whether a historical comparison is valid, or wants to learn from past events — even if they say 'this is like the dotcom bubble', 'history repeats itself', or 'what can we learn from how X handled this'.
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
Learn mode for explaining code, concepts, and architecture. Use when user asks to explain how things work, understand concepts, or learn about code patterns. Provides explanations from simple to complex with examples and analogies.
You must use this when seeking cross-domain analogies, applying first-principles reasoning, or overcoming creative bottlenecks.
Writes and edits prose in a plain and boring style: simple everyday words, complete sentences, no dashes, no jargon, and no analogies. Use when drafting or revising documents, Notion pages, reports, summaries, READMEs, emails, slides, commit messages, or PR descriptions, or when the user asks to simplify, clean up, tighten, reword, or make writing clearer. Use when the user invokes /plain-writing deslopify or asks to deslopify an agent response. Do not apply to code, only to the words around it.
Create visual analogies by mapping relational structure from familiar domains onto unfamiliar concepts using spatial relationships to make abstract patterns concrete. Covers static diagrams AND animated video storytelling (camera choreography, race comparisons, pacing). Use when explaining complex concepts, creating analogies, designing diagrams, creating explainer animations, or revealing system structure.
ELI5-style explanations with analogies and multiple examples. Explains concepts at different levels (ELI5, high school, undergraduate, graduate). Uses real-world analogies and visual metaphors. Use when explaining difficult concepts, clarifying confusing topics, or learning new subjects. Triggers - explain concept, ELI5, explain like I'm 5, what is, how does, why does, analogy for, simple explanation.
Identify motif-level structures in a piece of information, expand abstract relationships back into concrete observable phenomena, and then use wind tunnel testing to verify key causal relationships and boundaries. USE WHEN user says 'find structure', 'what is the motif', 'structure wind tunnel', 'underlying structure', 'don’t just do AB testing', or wants to explore the generative mechanism behind a problem. Only expand cross-domain sources or multi-motif combinations when explicitly requested by the user. NOT FOR general summaries, single analogies, factual queries, or execution tasks with a clear unique solution.
Create high-quality Obsidian study notes with rich analogies, diagrams, and structured explanations. Handles both single notes and multi-file topic sets. Use when creating study notes, summarising lecture content, building a knowledge base, or organising any learning material into Obsidian markdown. Triggers - create study notes, obsidian notes, study notes, organise notes, learning notes, note from lecture, note from PDF.