/smithery/skills

POST /api/smithery/skills

Price: 1 credit

Get one Smithery agent skill by its owner/name id. Returns the skill's full instruction text as published, its summary, the file listing of the skill package, and the MCP servers Smithery recommends alongside it with their registry ids.

How to use it

This is where the skill's actual instructions live: `content` is the published SKILL.md text, which is what you read to judge what the skill does or to reuse its procedure. The usage and star counts that /smithery/skills/search returns are not repeated here, so keep the search row if you need them. `recommended_servers` are MCP servers Smithery pairs with this skill and their ids work directly with /smithery/servers. An unknown id comes back as 412, not an empty result.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• skill string required — Smithery skill id in owner/name form, or the address of its Smithery page (examples: "anthropics/pdf", "openclaw/nano-pdf", "https://smithery.ai/skills/anthropics/pdf"; minLength: 1)

Response

• @type string (default: "SmitherySkillDetail")
• id string required
• url string required
• namespace string required
• alias string required
• description string nullable
• content string nullable
• files array (default: [])
  • @type string (default: "SmitherySkillFile")
  • path string required
  • name string nullable
  • entry_type string nullable
• recommended_servers array (default: [])
  • @type string (default: "SmitheryServer")
  • id string required
  • url string required
  • name string nullable
  • namespace string nullable
  • alias string nullable
  • uuid string nullable
  • description string nullable
  • homepage string nullable
  • icon_url string nullable
  • owner_id string nullable
  • use_count integer nullable
  • relevance_score number nullable
  • verified boolean nullable
  • by_smithery boolean nullable
  • is_deployed boolean nullable
  • remote boolean nullable
  • inactive boolean nullable
  • unlisted boolean nullable
  • created_at string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No Smithery skill carries this owner/name id Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.