Skip to Content
GatewaysSkills gateway

Skills gateway

A skill is a short instruction file (SKILL.md) that teaches an AI coding assistant how to do one thing. A Skills gateway turns each of its tools into such a file, following the open Agent Skills  format, and the almyty Skills command-line tool installs them into the coding assistants on your computer: Claude Code, Cursor, GitHub Copilot, Windsurf, Codex and 25 more. After that, you can ask your assistant “look up order NW-10428” and it knows how.

Gateway detail page

Create the gateway

  1. Open Gateways and click Create gateway.
  2. Under Protocol, pick Skills.
  3. Under Tools, pick a whole API or single tools. A draft tool can’t be offered until it is active.
  4. Give it a Name; its address follows from the name (Advanced changes the path and who can use it).
  5. Click Create gateway.

A Skills gateway has no access key of its own: the Skills tool signs in as you. Tool scoping on the gateway’s page changes which tools it offers. The gateway’s Integrations tab shows the exact commands to install it, keep it up to date and sign in.

Assigning tools on the gateway Tool scoping tab

Install the skills

Someone comfortable with a terminal runs two commands on their computer: one to sign in, one to install. Copy them from the Integrations tab, or see For developers below. From then on, the coding assistants on that computer can use the gateway’s tools.

For developers

Sign in once (all almyty CLIs share one sign-in), then install:

npx @almyty/auth login
npx @almyty/auth login --token your-api-key   # CI: skip the browser
npx @almyty/skills install acme/my-skills

With a terminal, install shows a picker with the agents it detected already ticked; in CI or a pipe it writes to the detected agents plus .agents/skills/ (run --dry-run first to see where). It only touches the files it installed.

Keep them current. watch re-syncs one gateway every 60 seconds (--interval changes it); daemon re-syncs everything installed. Stop either with Ctrl+C.

npx @almyty/skills watch acme/my-skills

List and remove.

npx @almyty/skills gateways              # your gateways and the ref to install each
npx @almyty/skills list acme/my-skills   # the skills a gateway serves
npx @almyty/skills installed             # what is installed in this directory
npx @almyty/skills remove                # remove the almyty skills from this directory

See the Skills CLI for every command and option.

SKILL.md format

Each tool produces a markdown file whose frontmatter carries only name, description and a metadata block:

---
name: get_users
description: Retrieve a list of users with pagination
metadata:
  author: almyty
  generated: "true"
  toolId: "d3b0...-tool-uuid"
  version: "1"
---

The toolId is what almyty-skills run resolves against, so a skill keeps working after a rename. Under the frontmatter the file has a # get_users title, the tool’s description, then ## When to use, ## HTTP endpoint, ## Parameters, ## Example and ## Invocation sections.

## HTTP endpoint names the upstream API the tool wraps (for example GET https://api.example.com/users), not an almyty URL. Agents do not call it directly: ## Invocation gives them the Skills CLI command, which signs in with your stored almyty credentials and runs the tool through the gateway:

npm i -g @almyty/skills   # one-time, skip if already installed
almyty-skills run acme/my-skills/get_users --limit 10

npx -y @almyty/skills run ... works too, at roughly a second of startup per call.

Supported agents

The CLI knows 30 coding agents and where each keeps its skills:

Claude Code, Cursor, GitHub Copilot, Windsurf, Codex, Amp, Augment, Cline, CodeBuddy, Command Code, Continue, Cortex, Droid (Factory), Gemini CLI, Goose, Junie, Kilo Code, Kiro CLI, Kode, MCPJam, Mistral Vibe, Mux, OpenCode, OpenHands, Pi, Qoder, Qwen Code, Roo Code, Trae and Zencoder.

Any other agent that reads the universal .agents/skills/ directory picks them up too.

MCP gatewayTool scoping