pi-coding-agent-sdk
Pi Coding Agent SDK
Overview
Use this skill to explain the public @mariozechner/pi-coding-agent SDK, choose the right example or API surface, and build integrations that stay on exported APIs first.
Default to the public docs, examples, and packages/coding-agent/src/index.ts. Use source-level tracing only when the docs are ambiguous, incomplete, or the user explicitly asks where behavior lives in pi-mono.
If the task is about pi install, package manifests, distribution, or publishing a Pi package, use pi-package-creator instead of stretching this skill.
Task Routing
- Read
references/surface-and-examples.mdfor public exports, example selection, and “what should I import?” - Read
references/resource-loading-and-context.mdforDefaultResourceLoader, discovery rules,AGENTS.md, skills, prompts, and extension loading paths. - Read
references/tools-extensions-and-prompts.mdfor built-in tools, tool factories,customTools, extension-registered tools, prompt templates, slash-command behavior, and extension API boundaries. - Read
references/models-settings-sessions.mdforAuthStorage,ModelRegistry,SettingsManager,SessionManager, events, and run modes. - Read
references/source-crosswalk.mdonly when the docs/examples are not enough or the user asks where the SDK is implemented in pi-mono.
Default Workflow
More from mylesmcook/mcook-skills
adversarial-review
Use this skill when you need a serious code review, diff review, or implementation-plan review from independent reviewers. In Codex hosts, prefer a fresh Codex subagent for the Codex reviewer; otherwise use the Codex, Claude Code, and Gemini reviewer paths when available. Return a PASS, CONTESTED, or REJECT verdict.
13subagent-driven-development
Use after an implementation plan is approved to execute mostly independent tasks through fresh subagents with scoped context, harness-aware model routing, proportional review gates, and mandatory controller verification.
10brainerd
>
10simple-code
Reduce incidental complexity in code and design. Use when shaping APIs, module boundaries, refactors, tests, naming, and architecture tradeoffs with a bias toward concrete, local, reversible solutions.
7git-it-out
Use this skill when the user explicitly wants final end-of-session closeout and no more branch or PR limbo: proper verification, proper commits, main/mainline landing, push, repo-native merge/release/deploy/publish steps, tracker updates, Entire/checkpoint handling when configured, and a concise handoff. Reach for it on prompts like 'git it out', 'get it out', 'ship this', 'I'm done', 'I'm going to bed', 'take this off my plate', 'finish the session', or 'get this into production'. Do not use it for greenfield implementation, open-ended debugging, broad refactors, or inventing a release process from scratch.
7laws-of-taste
>-
6