Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →agentworkforce/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.
Passed 18 of 21 test cases with the skill, and 7 of 21 without it.
and 23 more in the full report
12 fixed7 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our workflow needs to connect Docker Hub to Relayfile using Composio as the auth backend. We want to verify the exact toolkit slug from the remote catalog before running the connect command, bypassing any cached local catalog entries. What exact CLI search command should we run?
| Checked | Without skill | With skill |
|---|---|---|
| Includes the --backend composio option in the catalog command. | Missed | Passed |
| Includes the --refresh flag to bypass local cache. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
After setup, files appear under <local-dir>/<provider>/...:
~/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)
Read = cat. Write = overwrite, create, or remove files in writable adapter resource directories. The mount daemon picks up the change, queues a writeback, and the cloud delivers to the provider's API.
Current mounts are also self-describing. Start with <local-dir>/LAYOUT.md, then read provider-specific <provider>/LAYOUT.md files and nearby _index.json files instead of hard-coding paths from memory. Entity filenames may use a <sanitized-name>__<id> convention, and some providers expose alias views such as by-title/, by-id/, by-name/, or by-state/.
relayfile CLI on $PATH. Verify: relayfile --help should list setup, integration, writeback, and the integration available / integration search / integration set-metadata subcommands.jq for JSON inspection. AWS CLI access is optional and only needed for internal cloud log diagnostics.agentrelay.com/cloud (cloud control plane), api.relayfile.dev (relayfile API), connect.nango.dev (Nango OAuth), and Composio connect endpoints when using --backend composio.test cases passed, vs 7 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.