From pi-skill
Authors Pi TypeScript extensions using ExtensionAPI, custom tools, commands, UI hooks, registerProvider, and resource path merging via extendResources. For building or debugging pi extensions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pi-skill:pi-extension-authoringThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Ground every answer in `pi-mono/` files below.
Ground every answer in pi-mono/ files below.
pi-mono/packages/coding-agent/docs/extensions.md — capabilities, lifecycle, patterns.pi-mono/packages/coding-agent/examples/extensions/README.md — runnable examples index.pi-mono/packages/coding-agent/src/core/resource-loader.ts — extendResources() appends paths via mergePaths after existing lastSkillPaths (late paths lose name collisions to earlier ones unless names differ).pi-mono/packages/coding-agent/src/core/agent-session.ts — extension commands vs queued prompts; skill expansion hooks.pi-mono/packages/coding-agent/docs/tui.md — extension TUI component integration with @mariozechner/pi-tui: Component rendering contract, overlay patterns, input handling in extension context.pi-mono/packages/coding-agent/docs/custom-provider.md — registerProvider() for proxies, OAuth/SSO, custom APIs, and custom model definitions.docs/extensions.md, not memory.pi-mono/packages/coding-agent/examples/extensions/ (e.g. dynamic-resources/ listing in examples README).docs/extensions.md, clone the closest examples/extensions/ template, then align with project AGENTS.md if working inside pi-mono.extendResources + mergePaths in resource-loader.ts to explain ordering with user/project/package skills.docs/tui.md for the Component rendering contract in extension context; combine with pi-tui skill for library-level APIs.pi-mono/packages/coding-agent/docs/custom-provider.md for registerProvider() OAuth flows and proxy patterns (grounded in pi-cli-workspace).npx claudepluginhub romiluz13/pi-agent-skillsGuides Pi CLI workspace: install, sessions, compaction, settings.json, skills, providers/auth, models, terminal editor, built-in tools (bash/read/edit), slash commands, CLI flags, tmux/Termux/Windows setup.
Guides selection of plugin component types (commands, skills, agents, hooks, MCP servers) via decision tree, covers lifecycle phases, and organization for scaling multi-component plugins.
Guides building, linking, testing, and publishing Gemini CLI Extensions including extension.yaml, GEMINI.md context, slash commands, MCP servers, and GitHub releases.