FruxonDocs
IntegrationsSkills

Updates an existing skill.

Full replace of the mutable fields on the skill. Agents that have this skill attached pick up the new instructions on their next turn — there is no per-conversation pinning. Built-in skills cannot be updated and will return 404.

PUT
/v1/tenants/{tenant}/skills/{skill}

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

skill*string

The unique identifier of the skill to update.

tenant*string

The tenant identifier

Request Body

The updated skill definition.

displayName?string|null
description?string|null
instructions?string|null
tools?|null
resources?|null
[key: string]?never

Response Body

curl -X PUT "https://api.fruxon.com/v1/tenants/string/skills/string" \  -H "Content-Type: application/json" \  -d '{}'
{
  "id": "string",
  "displayName": "string",
  "description": "string",
  "instructions": "string",
  "tools": [
    {
      "integrationId": "string",
      "id": "string"
    }
  ],
  "resources": [
    {
      "assetId": "string",
      "description": "string",
      "vectorized": false
    }
  ],
  "type": "SYSTEM",
  "createdAt": 0,
  "modifiedAt": 0
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Creates a new skill.

Persists a tenant-scoped skill and returns its assigned ID in the `Location` header. The skill becomes immediately eligible for agents in the same tenant — attach it via the agent configuration. To author the definition from a markdown file instead of writing it by hand, run `POST SkillGenerateFromMarkdown` or `POST SkillGenerateFromGitHub` first, then POST the result here.

Imports tools from a remote MCP server into an integration.

The integration is created automatically if it does not yet exist. Tools that already exist within the integration are skipped unless `overrideExisting` is set.