Loading...
Loading...
Found 61 Skills
Use when working with Obsidian vaults, markdown notes with [[wikilinks]], ![[embeds]], callouts (> [!type]), YAML frontmatter/properties, #tags, block IDs (^id), ==highlights==, %%comments%%, Obsidian CLI commands (obsidian create/read/append/search/move/tags/daily/etc.), vault organization (PARA, MOC, flat+tags, Johnny Decimal), folder restructuring, daily notes, templates, task management, backlink analysis, or any file operations in an Obsidian vault directory. Trigger this skill whenever the user mentions Obsidian, .md files inside an Obsidian vault, knowledge base organization, or note-taking workflows — even if they don't explicitly say "Obsidian".
Siro platform help — AI field sales coaching via mobile recording, real-time Halftime mid-call coaching, automated CRM data capture, conversation analytics, follow-up draft generation. Use when setting up Siro for a field sales team, configuring Siro CRM integration with Salesforce or HubSpot via Merge, Siro recording quality or battery drain issues on job sites, building a custom integration with Siro's REST API and webhooks, comparing Siro vs Rilla vs SalesAsk for field sales coaching, or Siro coaching prompts feel too generic for your vertical. Do NOT use for virtual/video meeting note-taking (use /sales-note-taker) or building a coaching program (use /sales-coaching).
Paper Reader for Non-Academics. It takes a research paper and extracts actionable ideas for personal use. Focuses on comprehension rather than academic critique. Activate when users share an arXiv link, paper URL, PDF, or request to analyze a research paper. Trigger words: 'read paper', 'analyze paper', 'paper', or when users share an academic paper.
Deep concept anatomist that deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy) and compresses insights into an epiphany. Use when user asks to explain, dissect, or deeply understand a concept, term, or idea. Triggers on '解剖概念', '概念解剖', 'explain concept', 'learn concept', '/ljg-learn'. Produces org-mode output.
Arrow of Root Tracing - a vertical deep-dive thinking tool. Given an opinion, phenomenon or problem, it drills all the way down like an arrow to the irreducible essence. Use when user says '想透', '追本', '本质是什么', '为什么会这样', '深挖', '钻到底', 'think deep', 'drill down', or wants to trace any idea/phenomenon vertically to its irreducible root. Also trigger when user provides a statement and wants depth analysis, not breadth survey.
Book Teardown. Calm, concise, sharp, and straightforward. Explain five key points clearly: What question is the author answering? What unproven assumptions does the author base their argument on? What framework do they use to analyze the topic? What conclusions do they reach? Finally, a few sentences of God's-eye view compression of the entire book. Use this when the user says '拆书', '拆这本', '分析这本书', '这本书在讲什么', '上帝之眼看这本书', '压缩一本书', 'book', or shares a book name requesting structural analysis. DO NOT use for chapter summaries (use Fabric extract_wisdom), papers (use ljg-paper), deep dives into a single viewpoint (use ljg-think), or ranking within a field (use ljg-rank).
Deconstructs academic papers like an X-ray machine, extracting core contributions, critical assumptions, and napkin-worthy insights from research papers.
Use this skill when generating higher-level synthesis notes such as literature reviews, comparison matrices, project summaries, or other cross-note summaries inside the project knowledge base.
Saves learning notes from the current conversation as a markdown file. Use after a study session to record what you learned.
Use this skill when the user discusses experiment design, ablations, training runs, evaluation, baselines, metrics, failures, or result interpretation that should be logged into Obsidian experiment and result notes.
Use this skill when the user is discussing daily research work, TODOs, plans, standups, meetings, milestones, or general project progress that should be reflected in Obsidian daily notes, plan notes, and hub updates.
Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault or fix a broken setup.