Curate your own stack
The account flow suggests a maintainer workspace where you collect the exact skills your team wants to standardize.
Remote Skills
Build collections once, share them anywhere agents run
Curate, share, install
Build a skill collection. Share it anywhere. Install it on any agent.
This product is strongest when it is presented as a collection workflow: you gather the skills you want from GitHub-backed SKILL.md sources, publish them as one collection, and other people connect that collection to remote-skills in Codex, Claude, or Gemini.
Pick only the skills you wantShare with your team or publish openlyInstall into Codex, Claude, or Gemini
Collection distribution
From your curation page to everyone's agent
shared by collection id
My collection
Pick the exact skills you want, keep them under one collection, and decide how broadly that collection should spread.
Add skills from GitHub
Import the repositories and skill docs you actually want in your stack.
Share with a team
Standardize prompts, workflows, and operating practices across coworkers.
Publish for open source
Turn the same collection into a public package other builders can adopt.
Internal team playbooksOpen-source agent toolkitsRole-based starter collections
Install with remote-skills
Each user decides where the collection lands. Install the integration into the chosen agent, add the collection id, and reuse the same collection across different environments.
$ npx remote-skills install --codex
install only for Codex
$ npx remote-skills config add collection your-team-playbook
subscribe this environment to one collection
$ npx remote-skills install --codex --claude
reuse the same workflow across multiple agents
For maintainers
Keep one collection as the source of truth instead of manually copying instructions between tools or teammates.
For consumers
Choose the agent you already use and pull the collection into that runtime without changing the shared source.
Share beyond one machine
A collection is meant to travel: internally across teammates or externally as an open-source distribution surface.
Agent-specific install
Consumers are not locked into one runtime. They can wire the same collection into Codex, Claude, Gemini, or multiple targets.
Why this matters
One collection can become the common operating layer for many people and many agents.
The strongest story in this product is not just discovery. It is that one person or one team can curate a skill stack once, then distribute it in a form everyone else can install into their preferred agent runtime.
Build your collection
Start from your own collection page and keep adding the GitHub-based skills that fit your workflow.
Share it with a team or the public
A collection becomes a reusable package of operating knowledge that coworkers or open-source users can subscribe to.
Let each user choose the target agent
With `remote-skills`, every user can install into the agent they actually use instead of receiving a one-size-fits-all setup.
Start with your role
Build the collection if you curate the workflow. Install it if you consume the workflow.
The landing page now pushes the real product promise: compose the right set of skills, share that package with a team or the public, and let every user connect it to the agent they already use.