refactor: finish companion rename migration

Complete the remaining pi-to-companion rename across companion-os, web, vm-orchestrator, docker, and archived fixtures.

Verification:
- semantic rg sweeps for Pi/piConfig/getPi/.pi runtime references
- npm run check in apps/companion-os (fails in this worktree: biome not found)

Co-authored-by: Codex <noreply@openai.com>
This commit is contained in:
Harivansh Rathi 2026-03-10 07:39:32 -05:00
parent e8fe3d54af
commit 536241053c
303 changed files with 3603 additions and 3602 deletions

View file

@ -1,10 +1,10 @@
> pi can create skills. Ask it to build one for your use case.
> companion can create skills. Ask it to build one for your use case.
# Skills
Skills are self-contained capability packages that the agent loads on-demand. A skill provides specialized workflows, setup instructions, helper scripts, and reference documentation for specific tasks.
Pi implements the [Agent Skills standard](https://agentskills.io/specification), warning about violations but remaining lenient.
Companion implements the [Agent Skills standard](https://agentskills.io/specification), warning about violations but remaining lenient.
## Table of Contents
@ -21,15 +21,15 @@ Pi implements the [Agent Skills standard](https://agentskills.io/specification),
> **Security:** Skills can instruct the model to perform any action and may include executable code the model invokes. Review skill content before use.
Pi loads skills from:
Companion loads skills from:
- Global:
- `~/.pi/agent/skills/`
- `~/.companion/agent/skills/`
- `~/.agents/skills/`
- Project:
- `.pi/skills/`
- `.companion/skills/`
- `.agents/skills/` in `cwd` and ancestor directories (up to git repo root, or filesystem root when not in a repo)
- Packages: `skills/` directories or `pi.skills` entries in `package.json`
- Packages: `skills/` directories or `companion.skills` entries in `package.json`
- Settings: `skills` array with files or directories
- CLI: `--skill <path>` (repeatable, additive even with `--no-skills`)
@ -50,7 +50,7 @@ To use skills from Claude Code or OpenAI Codex, add their directories to setting
}
```
For project-level Claude Code skills, add to `.pi/settings.json`:
For project-level Claude Code skills, add to `.companion/settings.json`:
```json
{
@ -60,7 +60,7 @@ For project-level Claude Code skills, add to `.pi/settings.json`:
## How Skills Work
1. At startup, pi scans skill locations and extracts names and descriptions
1. At startup, companion scans skill locations and extracts names and descriptions
2. The system prompt includes available skills in XML format per the [specification](https://agentskills.io/integrate-skills)
3. When a task matches, the agent uses `read` to load the full SKILL.md (models don't always do this; use prompting or `/skill:name` to force it)
4. The agent follows the instructions, using relative paths to reference scripts and assets
@ -174,7 +174,7 @@ description: Helps with PDFs.
## Validation
Pi validates skills against the Agent Skills standard. Most issues produce warnings but still load the skill:
Companion validates skills against the Agent Skills standard. Most issues produce warnings but still load the skill:
- Name doesn't match parent directory
- Name exceeds 64 characters or contains invalid characters
@ -229,4 +229,4 @@ cd /path/to/brave-search && npm install
## Skill Repositories
- [Anthropic Skills](https://github.com/anthropics/skills) - Document processing (docx, pdf, pptx, xlsx), web development
- [Pi Skills](https://github.com/badlogic/pi-skills) - Web search, browser automation, Google APIs, transcription
- [Companion Skills](https://github.com/badlogic/companion-skills) - Web search, browser automation, Google APIs, transcription