skilld

Developers

Search the registry from your Agent or your own code. The skilld CLI, the MCP server, and the skilld API read the same curated Skills.

Choose how to connect

Call the skilld API

  1. Create a skilld token

    Public operations need no token. Create one for account operations, such as watching a Repository. The same skilld token works in scripts and the CLI.

    Guests get 60 requests per minute per IP. Sign in or send a skilld token for 600 per account. These limits apply per Cloudflare location. If you reach a limit, wait 60 seconds, then retry.

    Label: API script. Expires in 90 days.

    Manage tokens

    Save this in your .env file. Keep that file out of source control.

    SKILLD_TOKEN="paste-your-token-here"

  2. Call your first operation

    Search needs no token. The answer is plain JSON: the matching Skills in items, and their count in total.

    curl 'https://skilld.dev/api/v1/skills?q=tailwind'

  3. Query trending Skills

    Read the weekly board without a token. Use window=month for the monthly board.

    curl 'https://skilld.dev/api/v1/trending?window=week&limit=10'

  4. Browse every operation

    The OpenAPI document lists every operation with its input, its answer, its errors, and an example.

    Read the OpenAPI document

  5. Code samples

    The watch sends the token from step 01. Load your .env file into your shell first.

    set -a . ./.env set +a

    # Read one Skill with its provenance curl 'https://skilld.dev/api/v1/skills/vercel-labs/agent-skills/web-design-guidelines' # Watch its Repository. Account operations send the token. curl -X PUT 'https://skilld.dev/api/v1/account/watches/vercel-labs/agent-skills' \ -H "Authorization: Bearer $SKILLD_TOKEN"

Where Agents look on their own