pi-extension

To scaffold a Pi extension, initialize a new project with a consistent structure including entry points, references, and assets. This establishes a standardized foundation for organizing tools, providers, and commands to support scalable extension development.

SKILL.md frontmatter in Pi extension development must strictly include both the name and description fields. Following this required format ensures your extension aligns with repository conventions and passes publishing guidelines for distribution.

Organize references and tools by structuring them within the recognized project directories for scripts, references, and assets. This workflow ensures all components are correctly recognized and aligned for end-to-end extension development.

Publishing guidelines for Pi extensions require enforcing proper SKILL.md frontmatter and organizing optional scripts, references, and assets. Following these repository conventions prepares your package for distribution and contribution to the Pi ecosystem.

You do not need to include optional scripts and assets when creating a Pi extension, as they are recognized but not strictly required. The mandatory requirements are a SKILL.md file with name and description frontmatter and standard entry points.

The best way to update a Pi extension is to review its entry points and ensure the SKILL.md frontmatter includes name and description. Reorganize references and tools to match the recognized workflow conventions for end-to-end development.