Create a Skill in Studio
Use Studio›Skills ↗ to package a reusable method, checklist, or procedure that an AI assistant can apply when a task matches.
A Skill is different from a saved Prompt. A Prompt stores reusable text or instructions. A Skill stores when to use a method, the method itself, and optional files such as examples, templates, or reference material.
By the end you will have a Skill with a clear description, instructions, visibility settings, and a test plan.
Time to complete: ~10 minutes
Prerequisites
- An active Studio account.
- A repeatable task you want to standardize. Good first candidates are review checklists, report formats, or domain-specific analysis steps.
Step 1: Open Skills
- Open Studio›Studio ↗.
- In the sidebar, open
Build>Skills. - Click
New Skill.
Step 2: Define when the Skill applies
Fill in the Skill details. The description is the most important field because it determines when the assistant loads the Skill.
| Field | Example |
|---|---|
Title | contract-risk-review |
Description | Use when reviewing customer contracts for renewal, liability, or termination risk. |
Write the description as a condition:
- Vague: "Helps with contracts."
- Specific: "Use when reviewing customer contracts to identify renewal dates, termination clauses, liability caps, and missing approvals."
Step 3: Write the instructions
In the instructions field, write the procedure the Skill follows:
When given a customer contract:
- Extract renewal date, notice period, termination rights, and liability cap.
- Flag missing approvals or unusual commercial terms.
- Return a summary table with Risk, Evidence, and Recommended action.
Do not invent missing terms. Mark unknown values as
Not found.
Keep the Skill focused on one job. If you need several unrelated procedures, create separate Skills with separate descriptions.
Step 4: Add files
Attach files when the Skill needs examples or reference material:
- A checklist in
checklist.md. - A preferred output template in
template.md. - A sample reviewed contract with comments.
Supporting files are subject to a file-count limit. If you need more material, split the method into smaller Skills or use focused reference files that the instructions call out explicitly. See Structure large Skills with progressive disclosure for guidance.
Step 5: Save the Skill
- Click
Create Skill. - Open the saved Skill from the
Skillslist. - Confirm the details page shows the title, description, instructions, attached files, and first version.
Step 6: Choose visibility and Vibe availability
From the Skill details page, control where the Skill is available:
- Click
Share. - Choose whether to keep the Skill private or share it with the entire workspace.
- If you want to use the Skill in Vibe, click
Publish to Vibe.
Private Skills are visible only to you. Workspace Skills can be found and used by members of the workspace.
Sharing and Vibe availability are separate controls: Share controls who can access the Skill in Studio, while Publish to Vibe makes the Skill available in Vibe.
Step 7: Test the Skill
- Open the surface where you want to use the Skill.
- Run a realistic task that matches the description.
- Compare the output with your expected format.
If you clicked Publish to Vibe, open Vibe Work and run the test there.
Step 8: Create a new version
Create a new version when you want to change the Skill without overwriting the version that assistants or workflows already use. Studio creates the new version after you save changes.
- Open the Skill from the
Skillslist. - Update the instructions or attached files.
- Add version notes that explain what changed, such as
Adds liability cap checksorUpdates the summary table format. - Click
Save. - Confirm the version history shows the new version.
Older versions stay available for review and rollback. Test the new version before promoting it for production use.
Verify
Your Skill is ready if:
- It appears in the Skills list.
- The description explains exactly when the Skill applies.
- The output follows the procedure, format, and constraints you wrote.
- Attached files are relevant and referenced by the instructions.
- Its visibility is correct: private to you or shared with the workspace.
- It is published to Vibe if you need to use it in Vibe Work.
- The version history shows your original version and the updated version.