setting-up-relayfile
Use when an agent or human needs to set up relayfile end-to-end so agents can read and write provider files through a local mount. Covers `relayfile setup`, dynamic integration discovery with `relayfile integration available/search`, Nango and Composio backend selection, Atlassian site selection and metadata, cloud login, OAuth/connect flows, mount verification, `RELAYFILE_LOCAL_DIR` handoff, writeback status and retry commands, and key May 2026 cloud-mount gotchas.
npx skills add AgentWorkforce/relay --skill setting-up-relayfile --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
### Overview Relayfile mounts a provider (Notion, Linear, Slack, GitHub, and other adapter-backed integrations) as ordinary files on disk so an agent can read and write through the filesystem instead of calling APIs. This skill is the canonical setup recipe. Follow it top-to-bottom for first-time setup; jump to **Recovering from breakage** if a working mount has gone wrong. ### When to use this skill - An agent needs read access to a provider (e.g., "summarize this Notion database"). - An agent needs to write back to a provider (e.g., "post a review on this Notion page", "update this Linear issue"). - A human is setting up a mount before delegating work to an agent. - A mount stopped reflecting changes and you need to diagnose where. ### What you get #### After setup, files appear under `<local-dir>/<provider>/...`: ```text ~/relayfile-mount/notion/ ├── databases/ │ ├── <slug>--<id>/ │ │ ├── metadata.json ← database schema (read-only) │ │ └── pages/ │ │ ├── <slug>--<id>.json ← page metadata │ │ └── <slug>--<id>/ │ │ ├── content.md ← page body (READ + WRITE) │ │ └── blocks/<id>.json ← raw Notion block tree └── pages/ ← top-level pages (not in a database) ``` ### Prerequisites - Rece
- Overview
- When to use this skill
- What you get
- Prerequisites
- Step 1 — Run setup (interactive happy path)
- Step 3 — Hand off to an agent
- Step 4 — Verify writeback works (optional but recommended)
- Discover writeback contracts before writing
- Path conventions per provider
- Adding more integrations after setup
- Common gotchas
- Recovering from breakage
- Cleaning up
- What this skill does NOT cover
relayfile status my-agent export RELAYFILE_LOCAL_DIR=~/relayfile-mount point Claude Code at the dir or `cd` in echo "[writeback test $(date -u +%FT%TZ)]" > ~/relayfile-mount/notion/pages/<throwaway-page>/content.md relayfile integration available --refresh relayfile integration search docker --backend composio --refresh relayfile integration available --backend nango --search notion curl -sS -X POST "https://agentrelay.com/cloud/api/v1/workspaces/<id>/integrations/connect-session" \ relayfile integration search <term> --backend composio --refresh relayfile integration search <term> --backend nango --refresh
What does the setting-up-relayfile skill do?
Use when an agent or human needs to set up relayfile end-to-end so agents can read and write provider files through a local mount. Covers `relayfile setup`, dynamic integration discovery with `relayfile integration available/search`, Nango and Composio backend selection, Atlassian site selection and metadata, cloud login, OAuth/connect flows, mount verification, `RELAYFILE_LOCAL_DIR` handoff, writeback status and retry commands, and key May 2026 cloud-mount gotchas.
How do I install it?
Run `npx skills add AgentWorkforce/relay --skill setting-up-relayfile --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From AgentWorkforce/relay, a repository with 784 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.