akapoor/pi-agent-skills
1
0
Fork 0
forked from phytec-internal/pi-agent-skills
Code Pull requests Activity
Skills for the pi coding agent
15 commits 1 branch 0 tags 86 KiB
  • Python 78.1%
  • Shell 21.9%
Find a file
Exact
Stefan Müller-Klieser e797585236 README: drop removed PDF skills, mark garage_s3 as WIP
2026-09-24 09:40:41 +02:00
forgejo_cli forgejo_cli: rewrite skill for upstream fj CLI 2026-09-23 09:43:24 +02:00
garage_s3 garage_s3: fix invalid multi-line YAML description in frontmatter 2026-09-24 09:28:20 +02:00
github_cli github_cli: rewrite skill for upstream gh CLI 2026-09-24 09:31:13 +02:00
install.sh Switch to settings-based skill registration; convert cli skills to SKILL.md 2026-09-09 18:11:58 +02:00
README.md README: drop removed PDF skills, mark garage_s3 as WIP 2026-09-24 09:40:41 +02:00

README.md

pi-agent-skills

Skills for the pi coding agent, synced across machines via Syncthing (~/sync/projects/ai/pi-agent-skills).

Skills

Skill Purpose
forgejo_cli Forgejo (forgejo.phytec.de): issues/PRs/repos via the upstream fj CLI
github_cli GitHub: issues/PRs/repos via the upstream gh CLI
garage_s3 Garage S3 (s3.phytec.de): list buckets, list/upload/download/delete objects, presigned links via the bundled garage_s3.py (boto3) — WIP, an extension/alternative CLI tool is planned

Integration with pi

This repo is registered directly in pi's settings — no copying:

{
  "skills": ["~/sync/projects/ai/pi-agent-skills"]
}

pi discovers every */SKILL.md recursively, so the repo is the single source of truth. Updates (git pull / Syncthing) are picked up on the next pi start.

To register on a new machine:

./install.sh

install.sh is idempotent; it just adds the repo path to the skills array in ~/.pi/agent/settings.json.

Adding a skill

  1. Create <skill-name>/ with a SKILL.md (required name + description frontmatter — see pi's skills docs).
  2. Keep helper scripts inside the skill directory and call them with relative paths from SKILL.md.
  3. Commit — done. Never store tokens in the repo (use ~/.env.* files).

Notes

  • forgejo_cli needs the upstream Forgejo CLI (fj) installed and authenticated (fj auth login), and a git checkout whose remote points to the Forgejo server.
  • github_cli needs the official GitHub CLI (gh) installed and authenticated (gh auth login). Pass --repo owner/repo when working outside a checkout.
  • garage_s3 needs boto3 and GARAGE_KEY/GARAGE_SECRET in ~/.env.garage.