ccc Semantic Code Search
cocoindex-io/cocoindex-code
Semantic code search and index management with the ccc CLI: the agent initializes, indexes and queries the project by concept, filtering by language or path.
Carry work across a chain of fresh agent contexts using a shared goal, compact baton, and durable record.
Install Relay
$ npx skills add jmfederico/pi-web --skill relay -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jmfederico/pi-web relay --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jmfederico/pi-web.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/relay .claude/skills/relay && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "relay" agent skill from https://github.com/jmfederico/pi-web/tree/main/skills/relay into .claude/skills/relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jmfederico/pi-web/tree/main/skills/relayType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jmfederico/pi-web --skill relay -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jmfederico/pi-web relay --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jmfederico/pi-web.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/relay .agents/skills/relay && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "relay" agent skill from https://github.com/jmfederico/pi-web/tree/main/skills/relay into .agents/skills/relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jmfederico/pi-web --skill relay -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jmfederico/pi-web relay --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jmfederico/pi-web.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/relay .cursor/skills/relay && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "relay" agent skill from https://github.com/jmfederico/pi-web/tree/main/skills/relay into .cursor/skills/relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jmfederico/pi-web.git --path skills/relay--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jmfederico/pi-web --skill relay -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jmfederico/pi-web relay --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jmfederico/pi-web.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/relay .gemini/skills/relay && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "relay" agent skill from https://github.com/jmfederico/pi-web/tree/main/skills/relay into .gemini/skills/relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jmfederico/pi-web relayInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jmfederico/pi-web --skill relay -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jmfederico/pi-web.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/relay .github/skills/relay && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "relay" agent skill from https://github.com/jmfederico/pi-web/tree/main/skills/relay into .github/skills/relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jmfederico/pi-web --skill relay -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jmfederico/pi-web relay --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jmfederico/pi-web.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/relay .opencode/skills/relay && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "relay" agent skill from https://github.com/jmfederico/pi-web/tree/main/skills/relay into .opencode/skills/relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
relay- GitHub stars
- 869
- Token cost
- ~959 tokens
- SKILL.md length
- 516 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Carry work across a chain of fresh agent contexts using a shared goal, compact baton, and durable record.
- A user invokes Relay
- SKILL.md covers Finish line over plan, Scope over script, Handoff over handhold and Record over memory, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Discusses the Relay method
What it does
Relay is an agent skill from jmfederico/pi-web. Carry work across a chain of fresh agent contexts using a shared goal, compact baton, and durable record. Use when a user invokes Relay, discusses the Relay method, prepares a Relay, or continues an active Relay. Do not load for generic multi-step work or ordinary delegation.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Codebase knowledge for agents. The repository describes itself as: Web UI for Pi Coding Agent that keeps sessions alive in real workspaces. The licence is MIT.
When your agent uses it
- A user invokes Relay
- Discusses the Relay method
- Prepares a Relay
- Continues an active Relay
Example prompts
- “/relay”
What it can do on your machine
Read from SKILL.md and the folder at commit 2961669. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
relayprinciple.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Relay loads about 959 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 516 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jmfederico/pi-web at commit 2961669, republished under its MIT licence (© jmfederico). 516 words, ~959 tokens.
Download SKILL.mdSave it as
.claude/skills/relay/SKILL.md (or your agent's skills folder).- name
- relay
- description
- Carry work across a chain of fresh agent contexts using a shared goal, compact baton, and durable record. Use when a user invokes Relay, discusses the Relay method, prepares a Relay, or continues an active Relay. Do not load for generic multi-step work or ordinary delegation.
Relay
A Relay carries work across fresh agent contexts until the agreed goal is reached or an agent needs human help. Each context owns one useful slice, called a leg. There is no standing coordinator or fixed set of agent roles.
Follow the Relay Principle: give agents a destination and enough continuity to act, rather than recreating a management structure around them.
Finish line over plan
Help the human express what they want built and how they will recognize it is done. Resolve material ambiguity before dispatch. An existing requirements document can supply the goal; reference it rather than rewriting it into a larger specification.
Keep the goal stable and the route adaptable. Each runner checks the finish line against the current work and chooses the next useful slice. Changing the goal requires human agreement; changing implementation or sequencing within scope does not.
Scope over script
Record the relay-specific boundaries, limitations, conditions, and clarifications needed to understand the request. Preserve technical requirements and any other details the human explicitly asks to include.
Do not invent an implementation roadmap, speculative requirements, or a new software process. Project instructions, skills, and harness conventions remain where they belong; each runner discovers and follows what applies to its work. A Relay does not replace or weaken those rules.
Handoff over handhold
A baton says where we are, not how you must work. Avoid suggesting or assigning the next slice: even a provisional suggestion can anchor the successor. Record remaining gaps and concrete dependencies instead, and trust the successor to inspect reality and choose its slice.
Choose a meaningful increment that fits one context, not the tiniest possible task. Investigation and related work can stay together. Leg boundaries protect context quality, not organizational ownership.
Finish ongoing work and preserve the state before starting at most one fresh successor. Handoff is the final operational action; only a user-facing summary follows. Do not watch or steer the successor.
Show full SKILL.md (195 more words)Show less
Record over memory
Keep three kinds of durable information:
- Goal: the agreed finish line and relay-specific scope. Current status cannot override it.
- Baton: current position, completed work, what remains, relevant evidence and decisions, useful pointers, and any blocker.
- History: concise entries recording each leg's result, decisions, artifacts, checks, and handoff or stop.
Keep the baton compact. Use history for targeted lookup, not mandatory reconstruction. Inspect the actual work as needed; the record saves rediscovering prior decisions, not reading the project.
Signal over spin
Stop when the finish line is met, with evidence. Completion does not require finding another improvement.
Stop visibly when progress needs human input: record the blocker, what was tried, and the specific decision or help needed. If successive legs keep revisiting the same issue without new evidence or meaningful progress, surface that stall instead of spawning another attempt.
Optional cleanup, hypothetical risks, and a desire for perfection are not reasons to prolong the chain. Revisit a settled decision when facts change or concrete evidence shows it was wrong, not merely because a fresh agent has arrived.
Tools, storage, and session creation belong to the environment-specific runner skill, not the definition of Relay.
© jmfederico, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/relay of jmfederico/pi-web.
Open the folder on GitHubat commit 2961669
Compare with similar skills
Relay next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Relay this skilljmfederico/pi-web | 869 | — | ~959 | Automated safety check: Pass | MIT | |
| ccc Semantic Code Searchcocoindex-io/cocoindex-code | 2.8k | — | ~938 | Automated safety check: Pass | Apache-2.0 | |
| Context Engineeringabashev/vfs-s3 | 106 | 9 repos | ~2.6k | Automated safety check: Notes | Apache-2.0 | |
| Repomix Codebase Packeryamadashy/repomix | 29k | — | ~1.3k | Automated safety check: Notes | MIT | |
| Codebase Handbook BuilderRuhan-Wang/Harness_Handbook | 333 | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| CodemapJordanCoin/codemap | 704 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Context Engineering
abashev/vfs-s3
Optimizes agent context setup. An agent skill from abashev/vfs-s3.
Repomix Codebase Packer
yamadashy/repomix
Packs a local directory or remote GitHub repository into one AI-friendly file with Repomix, then searches it to explore structure, find patterns and count tokens.
Codebase Handbook Builder
Ruhan-Wang/Harness_Handbook
Generates, refreshes, validates and uses a compact handbook that maps where a change touches in a repository, using the active Codex session and no external LLM API.
Codemap
JordanCoin/codemap
Gives an agent a quick map of a codebase's structure, dependencies, changes and handoffs, and tunes per-project config so the output stays code-first.
Repomix Context Skill
sopaco/deepwiki-rs
A skill your agent uses when an agent needs source code from the local repomix index under .terrain/agent/repomix.md (not committed; regenerate via Terrain scan).
More from jmfederico/pi-web
Changeset Changelog
jmfederico/pi-web
A skill your agent uses whenever the user asks about changelogs, Changesets, release notes, conventional commits, commit messages for release notes, or making user-visible project changes that…
npm Release Via GitHub Actions
jmfederico/pi-web
A skill your agent uses whenever the user asks for a new npm version, npm release, package release, new release, version bump, publishing to npm, cutting a GitHub release, tagging a release, or…
Testing Guide
jmfederico/pi-web
Repository-specific testing guide. An agent skill from jmfederico/pi-web.
Code Quality Architecture
jmfederico/pi-web
Project code quality and architecture expectations for implementation, refactoring, planning, and code review.
Documentation Guide
jmfederico/pi-web
Repository documentation placement and writing guidance. An agent skill from jmfederico/pi-web.
Relay Runner
jmfederico/pi-web
Prepare and run Relay legs in Pi: keep the goal, baton, and log durable, then hand off to one fresh session or stop visibly.
Related
Categories
Questions about Relay
What does Relay do?
Carry work across a chain of fresh agent contexts using a shared goal, compact baton, and durable record. Relay is an agent skill from jmfederico/pi-web. Carry work across a chain of fresh agent contexts using a shared goal, compact baton, and durable record.
When should I use Relay?
Relay fits situations like: A user invokes Relay; discusses the Relay method; prepares a Relay; continues an active Relay.
How do I install Relay in Claude Code?
Run `npx skills add jmfederico/pi-web --skill relay -a claude-code`. Or copy the skill folder (skills/relay in jmfederico/pi-web) into .claude/skills/relay in your project. Claude Code loads it when a task matches its description.
How do I install Relay in Codex?
Run `npx skills add jmfederico/pi-web --skill relay -a codex`. Or copy the skill folder (skills/relay in jmfederico/pi-web) into .agents/skills/relay in your project. Codex loads it when a task matches its description.
Can I use Relay in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jmfederico/pi-web --skill relay -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/relay, .gemini/skills/relay, .github/skills/relay and .opencode/skills/relay in your project.
What does Relay need to run?
SKILL.md names no scripts, command-line tools or credentials: Relay is instructions for the agent only.
Does Relay access the network?
SKILL.md names 1 domain. As links in the text: relayprinciple.ai. This is read from the text; nothing was executed.
Is Relay safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Relay use?
Relay is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Relay use?
About 959 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Relay?
Skills that share tags, products or a category with Relay: ccc Semantic Code Search (cocoindex-io/cocoindex-code, 2.8k stars), Context Engineering (abashev/vfs-s3, 106 stars), Repomix Codebase Packer (yamadashy/repomix, 29k stars) and Codebase Handbook Builder (Ruhan-Wang/Harness_Handbook, 333 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Relay?
jmfederico (a GitHub user) maintains it in jmfederico/pi-web, which has 869 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.
Source: jmfederico/pi-web on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.