메뉴
Synthesizes knowledge from your Readwise Reader library by prioritizing highlights and annotations across documents. Use when the user asks for references from their reading, wants to surface saved knowledge, or needs cross-document synthesis.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | knowledge-retrieval |
| description | Synthesizes knowledge from your Readwise Reader library by prioritizing highlights and annotations across documents. Use when the user asks for references from their reading, wants to surface saved knowledge, or needs cross-document synthesis. |
| metadata | {"author":"Fred Bliss","version":"1.0.0","last_verified":"2026-04-02"} |
The intelligence for surfacing useful knowledge from your Readwise Reader library. Goes beyond simple search to synthesize information across multiple saved documents, prioritize your own highlights and annotations, and connect saved knowledge to your current work.
Your own highlights and notes are the highest-signal content in your library. They represent what you found important enough to mark. Retrieval should always prioritize them.
1. Highlighted + annotated (you marked it AND wrote a note)
2. Highlighted (you marked it as important)
3. Annotated/noted at document level (you wrote about the document)
4. Partially read (you engaged with it)
5. Saved but unread (you saved it, so the topic mattered)
When multiple documents touch the same topic, synthesize rather than list:
Given a topic query, collect highlights from multiple documents and present a unified brief:
From your reading on "[topic]":
Key insights (from [N] documents):
1. [Synthesized point from multiple highlights]
- "[highlight]" (from [doc1])
- "[highlight]" (from [doc2])
2. [Another synthesized point]
- "[highlight]" (from [doc3])
Your notes:
- [Your annotation from doc1]
- [Your annotation from doc2]
When documents present different viewpoints on a topic:
Perspectives on "[topic]" from your library:
View 1: [Summary]
- From: [document title]
- Key point: "[highlight]"
View 2: [Summary]
- From: [document title]
- Key point: "[highlight]"
Your position (based on your notes):
- [Synthesized from your annotations]
When the user is working on something and asks for references:
Instead of:
Here are 5 articles about X.
Present as:
From your reading on [topic]:
For your [current task], these highlights are most relevant:
1. "[highlight]" -- supports [aspect of their work]
Source: [title] by [author]
2. "[highlight]" -- provides context on [related aspect]
Source: [title]
Background reading (saved but not yet highlighted):
- [Title] -- likely relevant based on summary
Opt the current project into down-tier model delegation by installing a standalone .claude/rules/model-delegation.md rule, optionally with pre-shaped .claude/agents/ definitions (fast-executor, task-coder) and an optional agent-state feedback layer. The rule tells Claude to route well-specified data and coding tasks to a cheaper model in a subagent, keeping judgment-heavy work in the main loop. Use when the user says "set up model routing", "set up model delegation", "use cheaper models for subagents", "delegate to a lower-power model", or wants to remove or update that rule.
Pre-share scan for leaked secrets and privacy-sensitive content. Wraps simonw/scan-for-secrets for literal matching (with JSON/URL/HTML/backslash/unicode escape variants) and composes a ripgrep regex pass for shape-based leaks (other users' home paths, emails, IPv4, MAC, JWTs, API keys). Use when user says "scan for secrets", "check for leaked credentials", "pre-share scan", "redact home paths", "PII scan", "strip my username from transcripts", "scan logs before publishing", "check before sharing", "audit before commit", "find leaked API keys", "scan agent transcript".
Convert JavaScript and TypeScript projects to use bun instead of npm/yarn/pnpm. Use when user asks to "migrate from npm to bun", "convert to bun", "switch package managers", "replace npm", or "use bun instead". Includes conversion tables and lock file migration. Core conventions auto-loaded via SessionStart hook; invoke /dev-conventions:bun-tooling for full reference.
Audit project dependencies for known vulnerabilities using uv audit (Python) and bun audit (JS/TS). Use when user says "audit dependencies", "check for vulnerabilities", "security audit", "check deps", "are my packages safe", "CVE check", "dependency security", "vulnerability scan". Invoke with /dev-conventions:dep-audit.
Documentation conventions: last-updated dates, lowercase filenames, internal/ subfolder for non-shared docs, session logs, and documenting the "why". Use when creating or updating documentation, READMEs, or design docs. Invoke with /dev-conventions:doc-conventions. Triggers on "write docs", "update README", "document this", "add a design doc", "session log".
Detailed Python/uv conversion reference. Core conventions auto-loaded via SessionStart hook; invoke /dev-conventions:python-tooling for full conversion tables. Use when you need the complete uv command mapping, version pinning strategy, or lock file workflow.