# Maintain custom Assistant skills

Custom skills describe how your organisation wants the Assistant to approach a task. Each skill has a name, description, instructions, category, and enabled state; supported skills can also carry a script field.

## Create a focused skill

Ask the Assistant to create a custom skill for a repeatable task. Name its purpose, inputs, desired result, and the checks it should make before proposing a change. Review the proposed text and organisational scope before applying.

Prefer a narrow playbook such as “review an unsuccessful invoice ingest” over a broad instruction to perform any available action. Explain which app, connection, or source the person must choose rather than embedding a private identifier that will be wrong for colleagues.

## Maintain and disable

List custom skills and open the relevant entry to inspect its current text. Propose updates to the name, description, instructions, category, or enabled state. Disable an obsolete skill when you want to preserve its text without offering it for ordinary use.

Deleting requires the applicable authority and explicit approval. Recreating a deleted skill creates a new item; its earlier identity and history do not automatically return.

## Understand its limits

Custom skill text does not grant new access, register a missing service tool, bypass an approval card, or turn an automated action into a human decision. The platform's active capabilities and the user's permissions determine what can run.

Do not put credentials into instructions or scripts. Connect the service through the ordinary connection flow. Keep instructions about business data separate from claims that a document's own text is trusted authority.

After editing, try the skill on representative non-production inputs and inspect the proposed actions. A well-written skill still needs the app and workflow checks described in the relevant guides.