Agent skill

Catalog Add Route

Add an endpoint or query parameter to a catalog plugin's OpenAPI spec.

Apache-2.0Auto-check passedBackend & APIs

Install Catalog Add Route

skills CLI

$ npx skills add kubeflow/hub --skill catalog-add-route -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install kubeflow/hub catalog-add-route --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/kubeflow/hub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/catalog-add-route .claude/skills/catalog-add-route && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "catalog-add-route" agent skill from https://github.com/kubeflow/hub/tree/main/.agents/skills/catalog-add-route into .claude/skills/catalog-add-route/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "catalog-add-route", 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

$skill-installer install https://github.com/kubeflow/hub/tree/main/.agents/skills/catalog-add-route

Type 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.

skills CLI

$ npx skills add kubeflow/hub --skill catalog-add-route -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install kubeflow/hub catalog-add-route --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kubeflow/hub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/catalog-add-route .agents/skills/catalog-add-route && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "catalog-add-route" agent skill from https://github.com/kubeflow/hub/tree/main/.agents/skills/catalog-add-route into .agents/skills/catalog-add-route/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "catalog-add-route", 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.

skills CLI

$ npx skills add kubeflow/hub --skill catalog-add-route -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install kubeflow/hub catalog-add-route --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kubeflow/hub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/catalog-add-route .cursor/skills/catalog-add-route && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "catalog-add-route" agent skill from https://github.com/kubeflow/hub/tree/main/.agents/skills/catalog-add-route into .cursor/skills/catalog-add-route/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "catalog-add-route", 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

$ gemini skills install https://github.com/kubeflow/hub.git --path .agents/skills/catalog-add-route

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add kubeflow/hub --skill catalog-add-route -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install kubeflow/hub catalog-add-route --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kubeflow/hub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/catalog-add-route .gemini/skills/catalog-add-route && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "catalog-add-route" agent skill from https://github.com/kubeflow/hub/tree/main/.agents/skills/catalog-add-route into .gemini/skills/catalog-add-route/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "catalog-add-route", 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.

GitHub CLI

$ gh skill install kubeflow/hub catalog-add-route

Installs 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).

skills CLI

$ npx skills add kubeflow/hub --skill catalog-add-route -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/kubeflow/hub.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/catalog-add-route .github/skills/catalog-add-route && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "catalog-add-route" agent skill from https://github.com/kubeflow/hub/tree/main/.agents/skills/catalog-add-route into .github/skills/catalog-add-route/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "catalog-add-route", 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.

skills CLI

$ npx skills add kubeflow/hub --skill catalog-add-route -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install kubeflow/hub catalog-add-route --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kubeflow/hub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/catalog-add-route .opencode/skills/catalog-add-route && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "catalog-add-route" agent skill from https://github.com/kubeflow/hub/tree/main/.agents/skills/catalog-add-route into .opencode/skills/catalog-add-route/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "catalog-add-route", 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: catalog-add-route
GitHub stars: 186
Token cost: ~1.3k tokens
SKILL.md length: 280 words
Files: 1
Skills in repo: 5
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Add an endpoint or query parameter to a catalog plugin's OpenAPI spec.

Works in 4 steps: Identify Plugin → What to Add → Gather Details + Edit Spec → …
Tasks that involve OpenAPI specifications
SKILL.md covers Phase 1: Identify Plugin, Phase 2: What to Add, Phase 3: Gather Details + Edit… and Phase 4: Report
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Catalog Add Route is an agent skill from kubeflow/hub. Add an endpoint or query parameter to a catalog plugin's OpenAPI spec. Guides the user through the spec edit, then recommends running /sync-catalog to propagate changes. Does not run sync automatically — the user may want to batch multiple route additions before syncing.

Its SKILL.md is about 1.3k 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 Backend & APIs, covering OpenAPI specifications. It works with OpenAPI. The repository describes itself as: Model Registry provides a single pane of glass for ML model developers to index and manage models, versions, and ML artifacts metadata. It fills a gap between model… The licence is Apache-2.0.

When your agent uses it

Tasks that involve OpenAPI specifications

Example prompts

“/catalog-add-route”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Identify Plugin
What to Add
Gather Details + Edit Spec
Report

What it can do on your machine

Read from SKILL.md and the folder at commit 6c27d56. 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 (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Catalog Add Route loads about 1.3k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 280 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~72
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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 kubeflow/hub at commit 6c27d56, republished under its Apache-2.0 licence (© kubeflow). 280 words, ~1,347 tokens.

Download SKILL.mdSave it as .claude/skills/catalog-add-route/SKILL.md (or your agent's skills folder).

name: catalog-add-route
description: Add an endpoint or query parameter to a catalog plugin's OpenAPI spec. Guides the user through the spec edit, then recommends running /sync-catalog to propagate changes. Does not run sync automatically — the user may want to batch multiple route additions before syncing.
user-invocable: true

Catalog Add Route

Add a new endpoint or query parameter to a catalog plugin's OpenAPI spec.

Phase 1: Identify Plugin

Ask which plugin. Validate that api/openapi/src/plugins/<name>.yaml exists. Read the current spec to understand existing endpoints.

Phase 2: What to Add

Ask the user what they want. Common options:

Add query parameter to the existing list endpoint
Add sub-resource endpoint (e.g., GET /agents/{id}/tools)
Add custom endpoint (user describes what they need)

Phase 3: Gather Details + Edit Spec

Option 1: Add query parameter

Ask:

Parameter name (snake_case, e.g., provider, tags, verified)
Type: string, boolean, array (of strings), integer
Description (one line)
Required? (default: false)

Read the plugin spec's list endpoint. Add the parameter before the $ref pagination parameters, following the existing pattern:

yaml

- name: <param_name>
  description: <description>
  schema:
    type: <type>          # or for arrays:
    # type: array
    # items:
    #   type: string
  in: query
  required: false

For a filterQuery parameter (advanced SQL-like filtering), use the shared ref:

yaml

- $ref: "#/components/parameters/filterQuery"

This is defined in api/openapi/src/lib/common.yaml.

Option 2: Add sub-resource endpoint

Ask:

Sub-resource name (e.g., tools, artifacts, metrics)
Parent path parameter name (e.g., id, agent_id)
Sub-resource fields (name + type pairs, like the entity fields)
Should there be a list endpoint, get-by-id endpoint, or both?

Add to the spec following the model plugin's artifact pattern (reference: api/openapi/src/plugins/model.yaml, the artifacts endpoints):

List sub-resource:

yaml

  /api/<name>_catalog/v1alpha1/<entity>s/{<parent_id>}/<sub_resource>s:
    get:
      summary: List <sub_resource>s for a <entity>.
      tags:
        - <PascalName>CatalogService
      parameters:
        - name: <parent_id>
          description: The parent entity ID.
          schema:
            type: string
          in: path
          required: true
        - $ref: "#/components/parameters/pageSize"
        - $ref: "#/components/parameters/orderBy"
        - $ref: "#/components/parameters/sortOrder"
        - $ref: "#/components/parameters/nextPageToken"
      responses:
        "200":
          $ref: "#/components/responses/<SubResource>ListResponse"
        "401":
          $ref: "#/components/responses/Unauthorized"
        "404":
          $ref: "#/components/responses/NotFound"
        "500":
          $ref: "#/components/responses/InternalServerError"
      operationId: getAll<Entity><SubResource>s

Get sub-resource:

yaml

  /api/<name>_catalog/v1alpha1/<entity>s/{<parent_id>}/<sub_resource>s/{<sub_id>}:
    get:
      summary: Get a <sub_resource> by ID.
      tags:
        - <PascalName>CatalogService
      parameters:
        - name: <parent_id>
          ...
        - name: <sub_id>
          ...
      responses:
        "200":
          $ref: "#/components/responses/<SubResource>Response"
        ...
      operationId: get<Entity><SubResource>

Also add the sub-resource schema and response definitions under components:

yaml

components:
  schemas:
    <SubResource>:
      type: object
      properties:
        id:
          type: string
        name:
          type: string
        # ... sub-resource fields

    <SubResource>List:
      type: object
      properties:
        items:
          type: array
          items:
            $ref: "#/components/schemas/<SubResource>"
        nextPageToken:
          type: string
        pageSize:
          type: integer
        size:
          type: integer

  responses:
    <SubResource>ListResponse:
      description: A list of <sub_resource> entities.
      content:
        application/json:
          schema:
            $ref: "#/components/schemas/<SubResource>List"
    <SubResource>Response:
      description: A single <sub_resource> entity.
      content:
        application/json:
          schema:
            $ref: "#/components/schemas/<SubResource>"

Option 3: Custom endpoint

Ask the user to describe the endpoint (path, method, purpose). Generate the YAML following the conventions above. Use the tag <PascalName>CatalogService and derive the operationId from the path + method.

Naming conventions

Follow these patterns consistently:

OperationId: find<Entity>s (list), get<Entity> (get), getAll<Parent><Child>s (sub-list)
Tags: Always <PascalName>CatalogService
Response refs: <Entity>ListResponse, <Entity>Response
Path segments: snake_case plural (e.g., /agents, /tools)

Phase 4: Report

Print what was added to the spec and suggest next steps:

Added to api/openapi/src/plugins/<name>.yaml:
  - <description of what was added>

Next: run /sync-catalog to regenerate server stubs and wire the new endpoint.
If you want to add more routes first, run /catalog-add-route again.

Files

Just SKILL.md in .agents/skills/catalog-add-route of kubeflow/hub.

Open the folder on GitHubat commit 6c27d56

Compare with similar skills

Catalog Add Route 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.

Catalog Add Route compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Catalog Add Route this skillkubeflow/hub	186	—	~1.3k	Automated safety check: Pass	Apache-2.0	yesterday
ToolJet Marketplace Plugin BuilderToolJet/ToolJet	41k	—	~2.1k	Automated safety check: Pass	AGPL-3.0	yesterday
Step Partsearthtojake/text-to-cad	19k	1 repos	~1.5k	Automated safety check: Pass	MIT	yesterday
OpenAPI to MCP Servermcp-use/mcp-use	11k	—	~5.2k	Automated safety check: Pass	Apache-2.0	2 days ago
Use Yaakmountain-loop/yaak	19k	—	~1.9k	Automated safety check: Pass	MIT	today
API DesignerJeffallan/claude-skills	12k	1 repos	~2k	Automated safety check: Pass	MIT	7 days ago

Similar skills

ToolJet Marketplace Plugin Builder
ToolJet/ToolJet
Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.
41k GitHub stars~2.1k tokensUpdated yesterday
Backend & APIsAuto-check passed
Step Parts
earthtojake/text-to-cad
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers…
19k GitHub starsUsed in 1 repo~1.5k tokens
Backend & APIsAuto-check passed
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
11k GitHub stars~5.2k tokensUpdated 2 days ago
Backend & APIsAuto-check passed
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
19k GitHub stars~1.9k tokensUpdated today
Backend & APIsAuto-check passed
API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
12k GitHub starsUsed in 1 repo~2k tokens
Backend & APIsAuto-check passed
CLI Creator
huangruiteng/CS-Notes
Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script.
4k GitHub starsUsed in 2 repos~2.7k tokens
Backend & APIsAuto-check passed

Questions about Catalog Add Route

What does Catalog Add Route do?

Add an endpoint or query parameter to a catalog plugin's OpenAPI spec. Catalog Add Route is an agent skill from kubeflow/hub. Add an endpoint or query parameter to a catalog plugin's OpenAPI spec.

When should I use Catalog Add Route?

Catalog Add Route fits situations like: tasks that involve OpenAPI specifications.

How do I install Catalog Add Route in Claude Code?

Run `npx skills add kubeflow/hub --skill catalog-add-route -a claude-code`. Or copy the skill folder (.agents/skills/catalog-add-route in kubeflow/hub) into .claude/skills/catalog-add-route in your project. Claude Code loads it when a task matches its description.

How do I install Catalog Add Route in Codex?

Run `npx skills add kubeflow/hub --skill catalog-add-route -a codex`. Or copy the skill folder (.agents/skills/catalog-add-route in kubeflow/hub) into .agents/skills/catalog-add-route in your project. Codex loads it when a task matches its description.

Can I use Catalog Add Route 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 kubeflow/hub --skill catalog-add-route -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/catalog-add-route, .gemini/skills/catalog-add-route, .github/skills/catalog-add-route and .opencode/skills/catalog-add-route in your project.

What does Catalog Add Route need to run?

SKILL.md names no scripts, command-line tools or credentials: Catalog Add Route is instructions for the agent only.

Does Catalog Add Route access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Catalog Add Route 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 Catalog Add Route use?

Catalog Add Route is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Catalog Add Route use?

About 1.3k tokens (SKILL.md is roughly 5.4k 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 Catalog Add Route?

Skills that share tags, products or a category with Catalog Add Route: ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars), Step Parts (earthtojake/text-to-cad, 19k stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars) and Use Yaak (mountain-loop/yaak, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Catalog Add Route?

kubeflow (a GitHub organization) maintains it in kubeflow/hub, which has 186 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.

Source: kubeflow/hub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Catalog Add Route

Install Catalog Add Route

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Catalog Add Route

Phase 1: Identify Plugin

Phase 2: What to Add

Phase 3: Gather Details + Edit Spec

Option 1: Add query parameter

Option 2: Add sub-resource endpoint

Option 3: Custom endpoint

Naming conventions

Phase 4: Report

Files

Compare with similar skills

Similar skills

ToolJet Marketplace Plugin Builder

Step Parts

OpenAPI to MCP Server

Use Yaak

API Designer

CLI Creator

More from kubeflow/hub

Catalog Sample Data

Create Agent Catalog Source

Init Catalog

Sync Catalog

Questions about Catalog Add Route

Install Catalog Add Route

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Catalog Add Route

Phase 1: Identify Plugin

Phase 2: What to Add

Phase 3: Gather Details + Edit Spec

Option 1: Add query parameter

Option 2: Add sub-resource endpoint

Option 3: Custom endpoint

Naming conventions

Phase 4: Report

Files

Compare with similar skills

Similar skills

More from kubeflow/hub

Related

Questions about Catalog Add Route