菜单
Search Readwise highlights. Use when the user wants to find highlights, quotes, notes, or annotations from their reading library. Triggers on "search highlights", "find in readwise", "what did I highlight about", "my notes on".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/edwinhu/workflows --skill readwise-search命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use for feature development and engineering changes.
This skill should be used when the user asks to 'start data analysis', 'plan a data project', 'explore this dataset', 'what should I analyze', 'set up a new study', or needs the data-science workflow.
Use when the user asks to 'run a work workflow', 'do this properly', 'clarify, plan, and verify this', 'small structured task', or 'don't just wing it' for a bounded task too small for a specialized workflow.
正在显示 SKILL.md
基于 SOC 职业分类
| name | readwise-search |
| description | Search Readwise highlights. Use when the user wants to find highlights, quotes, notes, or annotations from their reading library. Triggers on "search highlights", "find in readwise", "what did I highlight about", "my notes on". |
| context | fork |
| agent | librarian |
| user-invocable | false |
1. Do you know the EXACT document or author?
YES -> Use fulltext filters (--full-text-queries)
NO -> Use vector search (semantic query)
2. Need document-level results (not highlights)?
YES -> Use `readwise reader-search-documents --query "term"`
or `readwise reader-list-documents` with --tag or --category filters
NO -> Use `readwise readwise-search-highlights`
3. Need keyword-exact match in highlight text?
YES -> Use `readwise-custom highlights --search "term"` (v2 API)
NO -> Use vector search
# Semantic search
readwise readwise-search-highlights --vector-search-term "fiduciary duty broker-dealer"
# With fulltext filters
readwise readwise-search-highlights --vector-search-term "regulation" \
--full-text-queries '[{"field_name": "document_author", "search_term": "Jackson"}]'
# JSON output for piping
readwise readwise-search-highlights --vector-search-term "query" --json
Fulltext filter fields (via --full-text-queries JSON array):
| field_name | Searches |
|---|---|
document_author | Document author name |
document_title | Document title |
highlight_note | Highlight notes/annotations |
highlight_plaintext | Highlight text content |
highlight_tags | Tags on highlights |
# Hybrid search across document content
readwise reader-search-documents --query "proxy advisors"
# With filters
readwise reader-search-documents --query "regulation" --author-search "Jackson" --category-in article
readwise reader-search-documents --query "proxy" --tags-in "corps" --location-in later,archive
# By tag (no search, just filter)
readwise reader-list-documents --tag "proxy advisors" --json
# By category and location
readwise reader-list-documents --category article --location archive
# Recent updates
readwise reader-list-documents --updated-after 2026-01-01T00:00:00Z --limit 20
# Exact text search across highlights (v2 API)
readwise-custom highlights --search "fiduciary" --limit 20 --json
| Need | Command | CLI |
|---|---|---|
| Semantic/conceptual highlight search | readwise readwise-search-highlights --vector-search-term "query" | Official |
| Hybrid document content search | readwise reader-search-documents --query "term" | Official |
| Keyword-exact match in highlights | readwise-custom highlights --search "term" | Custom |
| Documents by tag | readwise reader-list-documents --tag "X" | Official |
| Specific document | readwise reader-get-document-details --document-id <id> | Official |
Use --json for structured output. JSON search results include a score field (higher = more relevant, >0.01 typically meaningful).