Loading...
Loading...
Found 45 Skills
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).
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.
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.
Color-code the Obsidian graph view by rewriting `.obsidian/graph.json` colorGroups. Use this skill when the user says "color my graph", "color code obsidian", "colorize the graph", "color the graph by tag", "color by category", "highlight visibility in graph", "make the graph colorful", "distinguish tags in graph", or wants nodes in Obsidian's graph view tinted by tag, folder, or visibility. Generates a `colorGroups` array from the vault's actual tags/categories and merges it into the existing graph.json without clobbering other graph settings. Always backs up first.
Manage notes, bookmarks, and notebooks using the nb CLI. Create, list, search, and organize notes across multiple notebooks with Git-backed versioning.
Persistent markdown files as working memory for complex tasks: plan, track progress, store findings. Use when tasks have 3+ phases, require research, span many tool calls, or risk context drift. Use for "plan", "break down", "track progress", "multi-step", or complex tasks. Do NOT use for simple lookups, single-file edits, or questions answerable in one response.
Save the current conversation, answer, or insight into the Obsidian wiki vault as a structured note. Analyzes the chat, determines the right note type, creates frontmatter, files it in the correct wiki folder, and updates index, log, and hot cache. Triggers on: "save this", "save that answer", "/save", "file this", "save to wiki", "save this session", "file this conversation", "keep this", "save this analysis", "add this to the wiki".
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.
Interact with Heptabase using the CLI to create, read, and edit notes, journals, tags, and cards, and to browse AI Tutor goals, courses, and lessons. Use when the user asks to manage their Heptabase knowledge base, search cards, work with journals or tags, or read AI Tutor content.
[Manual Only] Record project learnings in FORyusuke.md. Structurally append lessons learned, pitfalls, debugging stories, and improvement points obtained during the session. It only works when explicitly called via /teach (it will not be triggered automatically in normal work).