/pi-context-pipeline
Orchestrate pi-finder and optional pi-librarian to produce a compact context pack and Codex kickoff prompt before coding.
$ npx -y skills add CoWork-OS/CoWork-OS --skill pi-context-pipeline --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-context-pipeline
Context preview
The summary Claude sees to decide when to auto-load this skill.
Orchestrate pi-finder and optional pi-librarian to produce a compact context pack and Codex kickoff prompt before coding.
SKILL.md
pi-context-pipeline.SKILL.mdname: pi-context-pipeline
description: "Orchestrate pi-finder and optional pi-librarian to produce a compact context pack and Codex kickoff prompt before coding."
Pi-context-pipeline
Purpose
Orchestrate pi-finder and optional pi-librarian to produce a compact context pack and Codex kickoff prompt before coding.
Routing
- Use when: Use when users want a Finder plus Librarian pre-coding pipeline that narrows context and prepares a coding handoff prompt.
- Do not use when: Do not use for direct coding changes that are already scoped to a few known files.
- Outputs: A local scout report, optional GitHub scout report, a compact context pack, and a Codex kickoff prompt under {artifactDir}.
- Success criteria: Produces focused artifacts with cited files/lines and a clean coding handoff that avoids unrelated context reads.
Trigger Examples
Positive
- Use the pi-context-pipeline skill for this request.
- Help me with pi-context-pipeline.
- Use when users want a Finder plus Librarian pre-coding pipeline that narrows context and prepares a coding handoff prompt.
- Pi-context-pipeline: provide an actionable result.
Negative
- Do not use for direct coding changes that are already scoped to a few known files.
- Do not use pi-context-pipeline for unrelated requests.
- This request is outside pi-context-pipeline scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | query | string | Yes | What to implement or investigate | | scope_hint | string | No | Optional local directories/files/symbols to prioritize | | repo_hints | string | No | Optional external repo hints (owner/repo list) | | owner_hints | string | No | Optional org/user hints for GitHub research | | run_librarian | boolean | No | Whether to include GitHub research in addition to local scouting | | max_search_results | number | No | Maximum GitHub search results requested by librarian |
Runtime Prompt
- Current runtime prompt length: 2187 characters.
- Runtime prompt is defined directly in `../pi-context-pipeline.json`.
Read more
name: pi-context-pipeline description: "Orchestrate pi-finder and optional pi-librarian to produce a compact context pack and Codex kickoff prompt before coding."
Pi-context-pipeline
Purpose
Orchestrate pi-finder and optional pi-librarian to produce a compact context pack and Codex kickoff prompt before coding.
Routing
- Use when: Use when users want a Finder plus Librarian pre-coding pipeline that narrows context and prepares a coding handoff prompt.
- Do not use when: Do not use for direct coding changes that are already scoped to a few known files.
- Outputs: A local scout report, optional GitHub scout report, a compact context pack, and a Codex kickoff prompt under {artifactDir}.
- Success criteria: Produces focused artifacts with cited files/lines and a clean coding handoff that avoids unrelated context reads.
Trigger Examples
Positive
- Use the pi-context-pipeline skill for this request.
- Help me with pi-context-pipeline.
- Use when users want a Finder plus Librarian pre-coding pipeline that narrows context and prepares a coding handoff prompt.
- Pi-context-pipeline: provide an actionable result.
Negative
- Do not use for direct coding changes that are already scoped to a few known files.
- Do not use pi-context-pipeline for unrelated requests.
- This request is outside pi-context-pipeline scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | query | string | Yes | What to implement or investigate | | scope_hint | string | No | Optional local directories/files/symbols to prioritize | | repo_hints | string | No | Optional external repo hints (owner/repo list) | | owner_hints | string | No | Optional org/user hints for GitHub research | | run_librarian | boolean | No | Whether to include GitHub research in addition to local scouting | | max_search_results | number | No | Maximum GitHub search results requested by librarian |
Runtime Prompt
- Current runtime prompt length: 2187 characters.
- Runtime prompt is defined directly in `../pi-context-pipeline.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