Skip to main content
Skills are reusable instructions. They help companions apply the same playbook each time a similar task comes up. Use a skill when you find yourself writing the same prompt, checklist, rubric, or process repeatedly. The easiest way to create a skill is from a chat that already went well. Tell the companion: 
Create a skill for me from this workflow.
The companion can summarize the steps, inputs, approval gates, and output format into reusable instructions for future tasks.

​
Global skills

Global skills are installed for your profile. Open them at strawberry://knowledge/skills. From a skill card, you can read or edit the skill instructions in the document viewer or start a chat that uses it.

​
Companion-specific skills

When you add a skill from companion settings, Strawberry creates it in that companion’s own Files -> [companion name] -> skills folder. Companion-specific skills:
  • Belong to that companion.
  • Appear before global skills in the slash menu.
  • Follow the companion when shared with another user or team.

​
What to put in a skill

A useful skill includes:
  • When to use it
  • What inputs to ask for
  • What sources to inspect
  • What steps to follow
  • What output format to produce
  • What requires user approval
  • How to verify the work

​
Turn good chats into skills

When a companion does something correctly, do not make yourself remember every detail. Ask it to capture the process. Useful follow-ups: 
Create a skill for me from what we just did.
Make sure it includes the questions you asked, the sources you checked,
the approval rules, and the final output format.

Update the skill so next time you ask for a sample size before running
the full workflow.
Review the draft before saving it. A good skill should still ask targeted questions when the task depends on missing context.

​
Example skill skeleton

# Skill: Competitor teardown

Use when the user asks to analyze a competitor's website, pricing,
positioning, product, or go-to-market motion.

Process:
1. Ask which competitor and what decision the user is trying to make.
2. Inspect official website pages first.
3. Capture pricing, target customer, core claims, integrations, and proof.
4. Compare findings to what you know about the user's company.
5. Return a concise battlecard with source links and confidence notes.

Ask before sending messages, signing up for products, or using paid tools.

​
Best practices

  • Keep skills focused.
  • Avoid stuffing unrelated workflows into one skill.
  • Include examples of good output.
  • Update skills after a companion makes a useful improvement.
  • Ask a companion to create or update the skill while the successful workflow is still fresh.
  • Use memory for facts and skills for process.