Skip to content
PitestsCLI & tooling

Move pi programming-philosophy skill to global scope

Session from 0xKobolds on Hugging Face by moikapy · MIT · condensed by Coders Talk

2msession
0interventions
GOAL

Make a project-specific pi skill (programming-philosophy) available globally across all projects rather than just in one repo.

  1. Prompt · +0
    Can you make the .pi/skills/programming-philosophy/ a skill used for all of my projects?
  2. Agent did · +0m
    Copied the skill directory into ~/.pi/skills/ and declared it done, claiming pi merges skills from project and global ~/.pi/skills/ locations.
  3. Fail · +1m
    Developer loaded pi and the skill wasn't there - the first fix was placed in the wrong directory.
  4. Agent did · +1m
    Investigated pi's actual global config directories and skills.md docs to find the real discovery path instead of guessing again.
  5. Agent did · +2m
    Discovered pi actually reads global skills via symlinks in ~/.pi/agent/skills/ pointing to real files in ~/.agents/skills/, matching the pattern of other existing skills like browser-use and chrome-cdp.
  6. Agent did · +2m
    Removed the skill from the wrong ~/.pi/skills/ location, copied it into ~/.agents/skills/, and created the correct symlink in ~/.pi/agent/skills/, then verified the symlink and directory contents matched other working skills.
  7. Outcome · +2m
    Skill correctly relocated to ~/.agents/skills/ with a matching symlink in ~/.pi/agent/skills/, following the same pattern as existing global skills.
VERDICT

Next time I'd ask it to check pi's actual skill discovery mechanism (docs or existing global skills) before moving anything, since the first attempt was just a guess at ~/.pi/skills/ that didn't work. What actually fixed it was noticing pi's real global skills were symlinks from ~/.pi/agent/skills/ into ~/.agents/skills/, and matching that exact pattern.

I tried this · 0

Discussion · 0

How Builds work