hyreflow-ai

hyreflow-ai Skills API

The Skills API from hyreflow-ai — 1 operation(s) for skills.

GitHub OpenAPI

Operations 1

GET /api/v2/skills/bundle Skills Bundle #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/hyreflow-ai/openapi/hyreflow-ai-skills-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/hyreflow-ai:hyreflow-ai-skills-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

hyreflow-ai-skills-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: hyreflow engine (local) Skills API
  version: 0.1.0
tags:
- name: Skills
paths:
  /api/v2/skills/bundle:
    get:
      summary: Skills Bundle
      description: 'gzip tarball of every skill package under skills/ (hyreflow-recruit + companions), preserving

        `/...` arcnames. The CLI installs each package into ~/.agents/skills and symlinks

        ~/.claude/skills.


        INTENTIONALLY PUBLIC (no auth). Reviewed decision (TODO "Public skill bundle"): the bootstrap

        `curl … | bash` installer runs `skills install` *before* `auth login`, so there is no bearer at

        fetch time. The packages carry NO secrets — every adapter is a thin vendor-API client that reads

        its key from the server-side engine env (managed) or the client''s own BYOK key; provider keys

        never ship in the bundle. The exposed asset is the playbook/recipe *source*, accepted as public.

        If this is ever reclassified as trade-secret IP, gate it behind a real client bearer and move

        `auth login` ahead of `skills install` in `_install_script`.


        Only real packages ship — a directory is one when it has a SKILL.md. Anything else that ends up

        alongside them (an editor/agent dropping a dotdir in there, a stray scratch folder) would otherwise be

        tarred up and served to every user on a public route, which is how internal notes leak.'
      operationId: skills_bundle_api_v2_skills_bundle_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Skills
components:
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer