web-fetcher
Web Fetcher
Fetch any URL as clean markdown. Two paths: known platforms go through OpenCLI (uses browser login state), everything else falls back through a chain of free markdown services.
Strategy Overview
- Known platforms (Twitter/X, zhihu, reddit, weibo, xiaohongshu, bilibili, etc.) → OpenCLI first. It uses the user's browser login state, is deterministic, and costs zero LLM tokens.
- Generic URLs (blogs, docs, articles) → Jina Reader > defuddle.md > markdown.new > WebFetch.
These are soft priorities — skip obviously wrong strategies (e.g., don't try OpenCLI for a random blog post, don't try Jina for a login-walled zhihu page).
Known Platform → OpenCLI Commands
More from jiahao-shao1/sjh-skills
notion-lifeos
User's personal Notion LifeOS (PARA: tasks, notes, projects, Make Time journals) with pre-configured DB IDs + API access — required for any LifeOS interaction. Use for adding tasks, taking notes, journaling, querying todos, searching notes, creating projects, reflection. Triggers: 'add task', 'take a note', 'what do I need to do', 'search my notes', '加个任务', '查笔记', '待办', '记录想法', '反思', '目标偏移'. Not for Notion API docs or workspace admin.
6cmux
Use this skill for ANY multi-pane or multi-agent terminal orchestration in cmux. Required when the user wants to: run things in parallel in separate terminal panes, split the terminal, spawn a sub-agent (Claude Code, Codex) in another pane, fan out tasks across splits, send keystrokes or text to another pane (including ctrl-c), read terminal output from another pane, update sidebar status or progress bar, open a URL in cmux's built-in browser pane, or display markdown preview alongside the terminal. The cmux CLI is the ONLY way to do these things — Bash cannot split panes or spawn agents. Trigger phrases: 'in parallel', 'split pane', 'spawn agent', 'fan out', 'new pane', 'browser pane', 'sidebar', 'send to pane', 'read from pane', 'show the plan', 'ctrl-c to', '分屏', '并行', '开个 pane'. NOT for: single command execution, basic bash operations, or questions about tmux.
5scholar-agent
Use this skill for anything related to academic paper discovery, filtering, reading, or management. Invoke for: browsing today's papers, getting paper recommendations, rating/collecting papers, deep-reading papers via NotebookLM, adding arXiv papers to NotebookLM, asking questions about papers, or checking trending research. This skill wraps the Scholar Inbox REST API and notebooklm-py CLI (recommended to install together for deep reading). Triggers: 'scholar inbox', 'paper digest', '看论文', '读论文', '论文推荐', 'rate papers', '收藏论文', '帮我筛选论文', '今天有什么论文', 'paper reader', 'deep read paper', 'trending papers', 'arXiv'. NOT for: reading PDFs, fetching web pages, writing literature reviews, general note-taking, or managing non-paper NotebookLM notebooks.
5daily-summary
>
4project-review
Strategic project review — automatically discovers and reads strategy documents (vision, roadmap, decisions, meeting notes, experiments), then generates a five-dimension analysis snapshot. Use when the user wants to review project direction, check strategic alignment, assess milestone progress, or get a quick overview before a team meeting. Triggers: 'project review', 'review the project', 'strategic review', 'where is the project at', 'project status overview', '项目全景', '审视战略', '战略 review', '项目现在什么状态', 'review 一下方向'. NOT for: code review, PR review, or any code-level review — this skill is about strategy, not code.
4codex-review
Get a second opinion from OpenAI Codex on your plan or code changes. Automatically detects whether to do a plan review or code review based on context. Claude and Codex iterate back-and-forth until Codex approves (max 5 rounds). Use whenever you want cross-model verification before implementing a plan or merging code — especially for architecture decisions, non-trivial refactors, config changes in critical systems, or when you're unsure about an approach. Triggers: '/codex-review', 'codex review', 'second opinion', 'let codex check', 'cross-check this', '让 codex 看看', '交叉审查', 'review with codex'. NOT for: trivial one-line fixes, formatting-only changes, or when user explicitly declines review.
3