Create a skill in Skill Studio
Skill Studio is where you create and edit your organization's skills, in the web console at /app. This page covers the two creation paths and the skill editor. To bring in a ready-made packaged skill, see Import via ZIP; to get it into users' hands, see Publish and version.
Creating and editing skills requires the skill administrator role (or org administrator) with access to at least one skill group. See Users & roles and Skill groups.
Where it lives
In the web console, open Skills. The conversational generator lives in Skill Studio (route /org/skill-studio). From the skill list you have two entry points to create:
- Create Skill — a quick form that synthesizes a draft.
- Skill Studio — a conversational assistant that discovers the process with you.
(The third button, Import from ZIP, is covered in Import via ZIP.)
Path A — "Create Skill"
The direct path: you provide the metadata and Studio creates a draft with a synthesized manifest, ready to edit.
- Click Create Skill.
- Fill in:
- Name — becomes the skill's Key. It follows the regex
^[a-z0-9][a-z0-9-]{1,98}[a-z0-9]$(lowercase, digits, and hyphens; no accents or spaces). - Group — the skill group the skill is born into. Required.
- Category — catalog category (e.g.
docs,sales). - Description — what the skill does. It's what helps the agent decide to invoke it, so be specific.
- Name — becomes the skill's Key. It follows the regex
- Confirm. Studio creates the draft and opens the editor, where you fine-tune the prompt, the files, and the secrets before publishing.
Path C — Conversational Skill Studio
When you know the process but not the manifest, describe it in natural language and the assistant builds the skill with you. The flow goes through phases:
| Phase | What happens |
|---|---|
| discovery | The assistant asks questions to understand the process, the inputs, and the outputs. |
| refining | It refines the steps, the arguments, and the permissions needed. |
| proposal | It presents a skill proposal (manifest + prompt) for you to review. |
| generating | It generates the skill's final content. |
At the end, Approve and Create Skill creates the skill and publishes it in one go. It's the path in the Create a business skill recipe.
The clearer the process — "takes a CSV of leads, generates a .docx proposal, uses the CRM token" — the better the manifest the assistant proposes. Explicitly mention any secret (token, key) the skill will need.
The skill editor
After you create (by either path), you land in the editor. It has five areas:
Metadata
Name, description, category, group, and the execution mode (radio: normal/protected — local_plain or local_protected). See Execution modes to choose.
Prompt Editor
The heart of the skill. Here you write the Prompt Content (the instructions the agent reads — the equivalent of SKILL.md) and the version's Changelog. A manifest banner validates the manifest as you edit and blocks publishing if it's invalid. Write the prompt the way the bundled skills do: say what not to fabricate, pin the outputs/ discipline, and document the exact entry point.
Files
The skill's file tree, split between the Draft (what you're editing) and the versions already published. The tabs show the manifest, the SKILL.md, the scripts, and the assets. This is where you add the code that does the work.
Env Secrets
Where you declare the secrets the skill needs and bind them. Imaginne injects a secret only if the skill declares it. The values themselves are registered by the org admin — see the author's side in Env-secrets and the registration in Env-secrets (admin).
Version History
The timeline of published versions, with rollback: creating a new version from an older one. See Publish and version for the versioning rules. The editor also shows which profiles use the skill.
From draft to publishing
Creating leaves the skill as a draft (except for the conversational path, which publishes right away). When it's ready:
- Make sure the manifest banner is green (valid manifest).
- Fill in the changelog.
- Publish — the skill gets a version and enters the catalog. See Publish and version.
Then, assign the skill to a profile so that users receive it in their next session.
See also
Was this page helpful?
Report a problem on this pageDo not send passwords, keys, tokens, or customer data.