/pi-librarian
GitHub research subagent for Pi that uses gh workflows to find and cite relevant repo files before implementation.
$ npx -y skills add CoWork-OS/CoWork-OS --skill pi-librarian --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/pi-librarian
Context preview
The summary Claude sees to decide when to auto-load this skill.
GitHub research subagent for Pi that uses gh workflows to find and cite relevant repo files before implementation.
SKILL.md
pi-librarian.SKILL.mdname: pi-librarian
description: "GitHub research subagent for Pi that uses gh workflows to find and cite relevant repo files before implementation."
Pi-librarian
Purpose
GitHub research subagent for Pi that uses gh workflows to find and cite relevant repo files before implementation.
Routing
- Use when: Use when users ask to research external GitHub repositories, compare implementation patterns, or gather cited repo evidence before coding.
- Do not use when: Do not use for local-workspace-only discovery or when GitHub access is unnecessary; use pi-finder-subagent instead.
- Outputs: A cited GitHub research report in {artifactDir}/librarian-report.md plus an actionable summary in {artifactDir}/librarian-summary.md.
- Success criteria: Librarian returns concrete repositories, file paths with citations, and clear unknowns/access limits that guide implementation decisions.
Trigger Examples
Positive
- Use the pi-librarian skill for this request.
- Help me with pi-librarian.
- Use when users ask to research external GitHub repositories, compare implementation patterns, or gather cited repo evidence before coding.
- Pi-librarian: provide an actionable result.
Negative
- Do not use for local-workspace-only discovery or when GitHub access is unnecessary; use pi-finder-subagent instead.
- Do not use pi-librarian for unrelated requests.
- This request is outside pi-librarian scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | query | string | Yes | What to research across GitHub repos | | repo_hints | string | No | Optional repo list hints, e.g. owner/repo pairs | | owner_hints | string | No | Optional owner/org hints | | max_search_results | number | No | Maximum gh search results to request |
Runtime Prompt
- Current runtime prompt length: 1003 characters.
- Runtime prompt is defined directly in `../pi-librarian.json`.
Read more
name: pi-librarian description: "GitHub research subagent for Pi that uses gh workflows to find and cite relevant repo files before implementation."
Pi-librarian
Purpose
GitHub research subagent for Pi that uses gh workflows to find and cite relevant repo files before implementation.
Routing
- Use when: Use when users ask to research external GitHub repositories, compare implementation patterns, or gather cited repo evidence before coding.
- Do not use when: Do not use for local-workspace-only discovery or when GitHub access is unnecessary; use pi-finder-subagent instead.
- Outputs: A cited GitHub research report in {artifactDir}/librarian-report.md plus an actionable summary in {artifactDir}/librarian-summary.md.
- Success criteria: Librarian returns concrete repositories, file paths with citations, and clear unknowns/access limits that guide implementation decisions.
Trigger Examples
Positive
- Use the pi-librarian skill for this request.
- Help me with pi-librarian.
- Use when users ask to research external GitHub repositories, compare implementation patterns, or gather cited repo evidence before coding.
- Pi-librarian: provide an actionable result.
Negative
- Do not use for local-workspace-only discovery or when GitHub access is unnecessary; use pi-finder-subagent instead.
- Do not use pi-librarian for unrelated requests.
- This request is outside pi-librarian scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | query | string | Yes | What to research across GitHub repos | | repo_hints | string | No | Optional repo list hints, e.g. owner/repo pairs | | owner_hints | string | No | Optional owner/org hints | | max_search_results | number | No | Maximum gh search results to request |
Runtime Prompt
- Current runtime prompt length: 1003 characters.
- Runtime prompt is defined directly in `../pi-librarian.json`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill