Skip to main content

Create a process skill

Goal: turn a repetitive process from your organization into a reusable skill — in this example, a sales-proposal generator — and make it available to your team. The flow goes from Skill Studio to publishing and to assignment by profile.

A skill packages the knowledge of the process (what to ask, how to structure the result) so that anyone authorized gets a consistent outcome. For the concept, see What skills are.

Prerequisites​

  • The skills admin or org admin role (creating and publishing skills requires one of these roles — see Users & roles).
  • Access to the console at /app.
  • At least one skill group (publishing requires choosing a group). Create one in Skill groups.

Step by step​

1. Describe the skill in Skill Studio​

  1. In the /app console, open Skills and enter Skill Studio (the conversational generator).
  2. Describe the process in plain language, for example: 
    I want a skill that generates a sales proposal. It should ask for:
    client name, project scope, timeline, and amount. With that, it should produce
    a document with: cover, executive summary, detailed scope, timeline,
    investment, and commercial terms. The final result is a .docx.
  3. The Studio runs the discovery → refining → proposal → generating phases, asking questions to finalize the design. Keep answering until the proposal reflects your process.
  4. Click Approve and Create Skill. The Studio creates the draft and publishes the skill.
Other ways to create

Besides the conversational Studio, the Skills page offers Create Skill (a form with Name/Group/Category/Description) and Import from ZIP (manifest + scripts). See Create a skill.

2. Review and adjust the draft​

In the skill editor you refine before (or after) publishing:

  • Metadata — confirm the execution mode (normal/local_plain or protected/local_protected). For most office processes, normal mode is enough. See Execution modes.
  • Prompt Editor — adjust the prompt content that guides the agent. A manifest banner blocks publishing while there's an error.
  • Env Secrets — if the skill needs credentials (e.g., an internal API), declare them here. See Environment secrets.

3. Publish​

  1. Set the version field (a semver string, e.g., 1.0.0) and write the changelog (required in the Studio).

  2. Choose the target group (required) and publish.

    Publishing is idempotent: the same version with the same content is a no-op; the same version with different content returns 422 ("bump the version"). Details in Publish a skill.

4. Assign to a profile​

Skills reach users through profiles. Without a profile that includes the skill, it won't show up for the user.

  1. In the console, open Profiles and edit (or create) the profile for the team that will use the skill — for example, "Sales".
  2. In the profile's Skills card, add the Proposal Generator.
  3. In the Users card, confirm that the right people are in the profile.

See Profiles.

5. Use it​

Clients sync skills at the start of the session. The authorized person simply asks:

Generate a sales proposal for the client Acme, scope of data migration,
8-week timeline, and an amount of R$ 120,000.

The agent recognizes the process, collects whatever is missing, and delivers the .docx.

Result​

A published skill, versioned and assigned to a profile — available to the entire authorized team, with a consistent result every time it's used. Future changes become new versions (with a changelog), and the policy is re-evaluated automatically after each publish.

See also​

Create a skill

The three Skill Studio paths in detail.

Open →Profiles

How to link skills to users.

Open →Publish a skill

Versioning, idempotency, and rollback.

Open →