pi-better-skills

🌐 Join the Community

[!NOTE] Building with AI doesn’t have to be a solo grind.
Join our Discord community to meet other people exploring the latest models, tools, workflows, and ideas: https://discord.gg/whhrDtCrSS

We talk about what’s new, what’s useful, and what’s actually worth paying attention to in AI.
And if you want more than conversation, members also get access to heavily discounted AI products and services — including deals on tools like ChatGPT Plus and more for just a few dollars.

pi-better-skills makes Pi skills resolve their bundled files from the skill directory, not from whatever project you are working in.

Pi implements the Agent Skills standard: small capability packages with a SKILL.md, helper scripts, reference files, templates, and assets. Many skills assume relative paths start at the skill folder. Pi runs tools from your current workspace, so a skill can say:

scripts/search.sh "query"

and the agent may try ./scripts/search.sh in your project instead of the skill’s own scripts/search.sh.

This extension gives the model the missing path context.

Install

pi install git:github.com/edxeth/pi-better-skills

pi-better-skills needs a POSIX environment (macOS, Linux). Windows paths are not supported.

New sessions load it automatically. Existing sessions need:

/reload

What it solves

Skills can bundle real tools

Good skills are more than prompt text. They often include scripts, examples, templates, reference markdown, or small CLIs. pi-better-skills helps the agent find those bundled resources from any project directory.

That means a skill can safely say:

scripts/exa.sh search "agent skills" 5

or:

Read reference/troubleshooting.md before continuing.

If the relative path does not exist in the workspace, the native read and bash tools fall back to the skill resource. Existing workspace files and directories take precedence, even when a skill contains the same path. Use $PI_SKILL_DIR/path or an absolute skill path to select the bundled resource explicitly.

Path checks use Pi’s workspace directory. They do not interpret directory changes inside shell commands. Custom tools keep their own path semantics.

Less path babysitting

Without this extension, users and skill authors have to over-explain paths:

• “First cd into the skill directory.”
• “Use the absolute path to this script.”
• “Do not run this from the project root.”
• “If it fails, retry with /home/.../skills/....”

pi-better-skills injects a small `` block when a SKILL.md is loaded, so the model sees where the skill lives and which paths belong to the skill versus the workspace.

The path and command guidance travels in two places: