Skills
pi-skills
Repository: badlogic/pi-skills
Layer thesis
How to read this part of the ecosystem
This is the shortest explanation of what this layer is for and why it matters.
What actually spreads through the ecosystem is not one canonical workflow. It is packages: skills, prompt templates, themes, extensions, and command bundles that can be cloned, symlinked, versioned, and shared.
Key artifacts
Best entry points in this layer
These projects explain this branch of the ecosystem fastest.
Extensions
agent-stuff (mitsupi)
agent-stuff is a public GitHub repository by mitsuhiko (Armin Ronacher) containing reusable skills, extensions, themes, distribution packages, and command wrappers for agent workflows, especially for Pi Coding Agent...
Discovered Related
pi-share-hf
Purpose: Publish redacted pi coding agent sessions from one OSS project to a Hugging Face dataset.
Work patterns
What people actually do here
These workflow slices connect the layer to real usage patterns.
Workflow pattern
Package the way you work
Once something is useful twice, the Pi ecosystem tends to turn it into a skill, extension, prompt template, theme, or npm/git package rather than keeping it as a private prompt trick.
Guardrails
What to remember while exploring
The layer-specific best-practice reminders that keep this branch legible.
Best practice
Prefer packages you can inspect, clone, and version
The healthiest Pi patterns are visible assets—skills, extensions, templates, themes, and package folders—not giant invisible prompts. They are easier to share, diff, adapt, and remove.
Best practice
Treat cross-runtime portability as a design advantage
Pi packages become more durable when they are not trapped in Pi alone. The ecosystem rewards artifacts that can travel to Claude Code, Codex CLI, Amp, or other shells with minimal adaptation.