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…
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.
/pi-context-pipelineContext 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.
name: pi-context-pipeline description: "Orchestrate pi-finder and optional pi-librarian to produce a compact context pack and Codex kickoff prompt before coding." version: "1.0.0" metadata: author: CoWork OS Contributors <info@coworkosapp.com>
Orchestrate pi-finder and optional pi-librarian to produce a compact context pack and Codex kickoff prompt before coding.
| 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 |
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
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…
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide…
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…
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,…
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.
Use when the user asks for a repository-wide or scoped-path security scan.