librarian
Research open-source libraries with evidence-backed answers and GitHub permalinks. Use when the user asks about library internals, needs implementation details with source code references, wants to understand why something was changed, or needs authoritative answers backed by actual code. Excels at navigating large open-source repos and providing citations to exact lines of code.
JetBrains · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add JetBrains/thinkrail --skill librarian技能说明
name: librarian description: Research open-source libraries with evidence-backed answers and GitHub permalinks. Use when the user asks about library internals, needs implementation details with source code references, wants to understand why something was changed, or needs authoritative answers backed by actual code. Excels at navigating large open-source repos and providing citations to exact lines of code.
Librarian
Answer questions about open-source libraries by finding evidence with GitHub permalinks. Every claim backed by actual code.
Execution Model
Pi runs the independent tool calls of one turn concurrently, and batching them saves LLM round-trips (~5-10s each). Use these patterns:
| Pattern | When | Actually parallel? |
|---|---|---|
| Batch tool calls in one turn | Independent ops (web_search + fetch_content + read) | Yes, and saves round-trips |
fetch_content({ urls: [...] }) | Multiple URLs to fetch | Yes (3 concurrent) |
Bash with & + wait | Multiple git/gh commands | Yes (OS-level) |
Step 1: Classify the Request
Before doing anything, classify the request to pick the right research strategy.
| Type | Trigger | Primary Approach |
|---|---|---|
| Conceptual | "How do I use X?", "Best practice for Y?" | web_search + fetch_content (README/docs) |
| Implementation | "How does X implement Y?", "Show me the source" | fetch_content (clone) + code search |
| Context/History | "Why was this changed?", "History of X?" | git log + git blame + issue/PR search |
| Comprehensive | Complex or ambiguous requests, "deep dive" | All of the above |
Step 2: Research by Type
Conceptual Questions
Batch these in one turn:
- web_search:
"library-name topic"for recent articles and discussions - fetch_content: the library's GitHub repo URL to clone and check README, docs, or examples
Synthesize web results + repo docs. Cite official documentation and link to relevant source files.
Implementation Questions
The core workflow -- clone, find, permalink:
- fetch_content the GitHub repo URL -- this clones it locally and returns the file tree after
Repository cloned to: <path>; that path is the clone, use it for every step below - Use bash to search the cloned repo:
grep -rn "function_name",find . -name "*.ts" - Use read to examine specific files once you've located them
- Get the commit SHA:
cd <clone path> && git rev-parse HEAD - Construct permalink:
https://github.com/owner/repo/blob/<sha>/path/to/file#L10-L20
Batch the initial calls: fetch_content (clone) + web_search (recent discussions) in one turn. Then dig into the clone with grep/read once it's available.
Context/History Questions
Use git operations on the cloned repo:
cd <clone path>
# Recent changes to a specific file
git log --oneline -n 20 -- path/to/file.ts
# Who changed what and when
git blame -L 10,30 path/to/file.ts
# Full diff for a specific commit
git show <sha> -- path/to/file.ts
# Search commit messages
git log --oneline --grep="keyword" -n 10
For issues and PRs, use bash:
# Search issues
gh search issues "keyword" --repo owner/repo --state all --limit 10
# Search merged PRs
gh search prs "keyword" --repo owner/repo --state merged --limit 10
# View specific issue/PR with comments
gh issue view <number> --repo owner/repo --comments
gh pr view <number> --repo owner/repo --comments
# Release notes
gh api repos/owner/repo/releases --jq '.[0:5] | .[].tag_name'
Comprehensive Research
Combine everything. Batch these in one turn:
- web_search: recent articles and discussions
- fetch_content: clone the repo (or multiple repos if comparing)
- bash:
gh search issues "keyword" --repo owner/repo --limit 10 & gh search prs "keyword" --repo owner/repo --state merged --limit 10 & wait
Then dig into the clone with grep, read, git blame, git log as needed.
Step 3: Construct Permalinks
Permalinks are the whole point. They make your answers citable and verifiable.
https://github.com/<owner>/<repo>/blob/<commit-sha>/<filepath>#L<start>-L<end>
Getting the SHA from a cloned repo:
cd <clone path> && git rev-parse HEAD
Getting the SHA from a tag:
gh api repos/owner/repo/git/refs/tags/v1.0.0 --jq '.object.sha'
Always use full commit SHAs, not branch names. Branch links break when code changes. Permalinks don't.
Step 4: Cite Everything
Every code-related claim needs a permalink. Format:
The stale time check happens in [`notifyManager.ts`](https://github.com/TanStack/query/blob/abc123/packages/query-core/src/notifyManager.ts#L42-L50):
\`\`\`typescript
function isStale(query: Query, staleTime: number): boolean {
return query.state.dataUpdatedAt + staleTime < Date.now()
}
\`\`\`
For conceptual answers, link to official docs and relevant source files. For implementation answers, every function/class reference should have a permalink.
Video Analysis
For questions about video tutorials, conference talks, or screen recordings:
// Full extraction (transcript + visual descriptions)
fetch_content({ url: "https://youtube.com/watch?v=abc" })
// Ask a specific question about a video
fetch_content({ url: "https://youtube.com/watch?v=abc", prompt: "What libraries are imported in this tutorial?" })
// Single frame at a known moment
fetch_content({ url: "https://youtube.com/watch?v=abc", timestamp: "23:41" })
// Range scan for visual discovery
fetch_content({ url: "https://youtube.com/watch?v=abc", timestamp: "23:41-25:00" })
// Custom density across a range
fetch_content({ url: "https://youtube.com/watch?v=abc", timestamp: "23:41-25:00", frames: 3 })
// Whole-video sampling
fetch_content({ url: "https://youtube.com/watch?v=abc", frames: 6 })
// Analyze a local recording
fetch_content({ url: "/path/to/demo.mp4", prompt: "What error message appears on screen?" })
// B
阅读完整来源 ↗