> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gocromo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Process Skills

> Capture reusable step-by-step routines that Cromo can apply in chat and evolve with your team.

A **Process Skill** is a reusable routine for the Cromo assistant. It preserves how your team performs a task so the same instructions can be applied in future conversations.

Skills are useful when a process is stable enough to reuse but still benefits from an interactive assistant and human judgment.

## Skill or Workflow?

| Use a Process Skill when…                       | Use a Workflow when…                            |
| ----------------------------------------------- | ----------------------------------------------- |
| A person starts the task in chat                | A trigger should start the process              |
| The assistant should adapt the steps to context | The steps should execute deterministically      |
| Human judgment is central                       | Inputs, outputs, and mappings are well defined  |
| You want a reusable operating method            | You need run status, retries, and audit history |

A Skill can help you prove a process before turning it into a Workflow.

## Create a Skill

You can create a Skill in two ways:

* **From Knowledge** — generate it from a reviewed how-to or process page.
* **Manually** — write the routine directly when the team already agrees on the steps.

A good Skill includes:

* a precise name and purpose;
* when to use it;
* required context or inputs;
* ordered steps;
* decision points and exceptions;
* the expected result;
* conditions that require human escalation.

## Example: renewal risk review

A Skill named **Review renewal risk** might instruct Cromo to:

1. read the customer record and renewal date;
2. compare the case with the Renewal Policy Knowledge page;
3. check whether value, risk, and next action are present;
4. identify missing evidence;
5. prepare questions for the account owner;
6. return a concise risk summary with citations.

A teammate can invoke this routine from chat for a single customer while keeping control of the final decision.

## Skill prompts to try

### Create from Knowledge

```text theme={null}
Create a Process Skill from the Customer Complaint Escalation page. The Skill
must classify severity, identify the applicable response target, recommend an
owner, list missing information, and return policy citations.
```

### Create manually

```text theme={null}
Create a Process Skill named Review an invoice exception. It should verify
required fields, check for overdue and unmatched invoices, distinguish possible
duplicates from confirmed duplicates, recommend a next action, and escalate
uncertain cases to a person.
```

Review the generated steps and add the exception cases an experienced teammate would expect.

## Review and activate

Skills generated from Knowledge can begin as candidates. Review the candidate before activating it:

* confirm the steps match the source page;
* remove ambiguous or outdated instructions;
* add exceptions and escalation rules;
* verify that the expected output is clear.

Members can create and manage Skills. Approval and activation require the automation approval permission, also available to Members, Admins, and Owners by default.

## Maintain Skills

Update a Skill when the underlying policy or operating process changes. If the Skill came from a Knowledge page, review both assets so they do not drift apart.

Deactivate a Skill that should no longer be used. Delete it only when the team no longer needs its definition or history.

<Tip>
  Write instructions for a capable teammate who is new to the process. Include the judgment criteria they would otherwise have to ask someone to explain.
</Tip>