Create Skill
Create a help desk skill for a team. The skill is saved as an unpublished draft unless is_published is true.
Authentication and permissions
Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
The ID of the team.
Short title identifying this skill (e.g. "Route password reset tickets to IT"). Shown in the skills list and in chips when the skill is referenced. Keep it descriptive but concise.
TRIGGER condition — when should the help desk agent invoke this skill? Plain prose answering "When should Serval use this skill?". Example: "When a ticket is about an SSO login failure or a user cannot access their Okta account."
BEHAVIOR instructions — how should the help desk agent handle the
situation when this skill fires? Plain prose answering "How should
Serval handle this situation?". Include the concrete steps,
workflows to run (use <@workflow:ID> mentions), who to escalate
to (use <@user:ID> mentions), and any relevant context.
Whether the help desk agent always uses this skill instead of selecting it by its description. Defaults to false.
Whether to publish the skill after creating it. Defaults to false, which saves an unpublished draft.
The channels where the help desk agent can use the skill. Omitted or empty selects every channel, including channels added later.
Response
Success
The created skill.

