extending-pi

Guides teams in choosing Pi extension types and structuring SKILL.md packaging.

446|40|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/tmustier/pi-extensions --skill extending-pi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extending-pi
Source: https://github.com/tmustier/pi-extensions/tree/main/extending-pi
Command: npx skills add https://github.com/tmustier/pi-extensions --skill extending-pi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Pi extension framework helps teams decide between building skills, extensions, templates, themes, or packaging, enabling structured growth of Pi capabilities.

Core Features & Use Cases

  • Clear decision guidance on what to build (Skill vs Extension vs Prompt Template vs Theme vs Context file vs Custom Model vs Package)
  • Nested sub-skills for detailed guidance (e.g., skill-creator)
  • Structured packaging and discovery guidelines to support scalable deployment

Quick Start

Start by reading the root SKILL.md and the nested skill-creator SKILL.md to begin planning your Pi extension strategy.

Frequently Asked Questions about extending-pi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide between building a Pi skill, extension, or prompt template?

To decide between Pi skills, extensions, prompt templates, themes, and context files, evaluate your end-to-end capability requirements and use the framework's structured guidelines to select the appropriate artifact type for your project.

What is the required structure for a Pi skill layout?

A Pi skill layout requires a root SKILL.md file with mandatory name and description frontmatter fields, and it can optionally include nested resources, scripts, references, and assets to support the skill's core functionality.

How do I package Pi extensions for team deployment across projects?

To package Pi extensions for scalable deployment, follow the framework's structured packaging and discovery guidelines, and execute the validation workflow to ensure your skill creation is compatible for distribution across multiple projects.

Can I use nested sub-skills for detailed Pi extension guidance?

Yes, you can use nested sub-skills, such as the skill-creator, to receive detailed guidance on planning your Pi extension strategy and building structured capabilities from concept to packaging.

What is the validation workflow for Pi skill packaging compatibility?

The Pi skill validation workflow ensures discovery and packaging compatibility by checking that your structured layout includes mandatory SKILL.md frontmatter fields and correctly configured optional resources before deployment.