Skills

Skills are how you teach Computer to do something the same way every time. Think of a skill as a small folder containing a set of instructions, plus optional scripts and reference files, packaged together so Computer can pick them up automatically when a relevant question comes in.

This article covers everything end-to-end: what a skill is, how to use the Skills page in the desktop app, how to write your own skill, how to test it, how to share it across your org, and how to troubleshoot when it isn't doing what you want.

Skills let your team package its best playbook into a reusable instruction set, so Computer follows the same steps, in the same order, with the same quality every time, instead of you re-explaining the process in every chat.

• Discover, install, and toggle Skills — Browse the marketplace, install with one click, and enable/disable per device from Settings → Skills.

• Org Skills — Admins publish a Skill once; everyone in the org gets it automatically. No install, no setup.

• My Skills (local) — Build personal Skills on the desktop app with scripts, references, and templates — not just a prompt file.

• skill-creator — A built-in Skill that helps you draft, refine, and iterate on new Skills conversationally.

• Progressive disclosure — Skills load only when they're relevant, so you can keep many enabled without bloating context.

A skill is a folder with a SKILL.md file plus optional supporting files. The SKILL.md tells Computer:

• What the skill does

• When to use it (the trigger conditions)

• The steps to follow when it's used

Instead of re-explaining your preferences, processes, and domain expertise in every conversation, you teach Computer once — and the skill is loaded automatically whenever a relevant request comes in.

Skills are most useful when you have repeatable workflows:

• Generating reports the same way every week

• Following your team's sales conventions

• Coordinating a multi-step process across tools (e.g. "create DevRev ticket, then post a comment, then fetch meeting from granola")

• Embedding domain knowledge (compliance checks, on-call procedures, sales motions)

They're not the right tool for one-off questions or simple tasks Computer can already do unaided.

The Skills page

• Discover — browse skills published in the DevRev marketplace. Install with one click.

• My Skills — skills you've installed locally on this device. Toggle each one on or off.

• Org Skills — skills published by your organization's admins. Available to everyone in the org, no install needed.

> 📝 Note: If you open My Skills on the web or mobile app, a banner prompts you to install the desktop app, because local skills run on desktop only.

Discover

The Discover tab is the marketplace. Skills here are vetted, packaged, and ready to install. Use the search bar to filter by name or category, then click a skill card to see its description and capabilities, and click Install to add it to My Skills.

My Skills (desktop only)

Each row shows the skill's name, description, and an enable/disable toggle. Toggles take effect the next time you invoke Computer, no restart needed.

Local skills run on your machine, so they can:

• Use your local working folder and files

• Run shell commands that need your local environment (with your sandboxing rules — see the Sandboxing section)

• Access integrations whose credentials you've authorized for the desktop app

Org Skills

Skills your admin has rolled out to the whole org. You can't enable / disable them per-device — they're always available.

Important distinction for the current release

Org skills is just a single prompt markdown file (and may reference tools). Admins create and push them; everyone gets them.

My Skills are local-by-default and personal to you. They can include scripts, multiple reference files, and a more complex folder structure.

Your local skills can't be promoted to org level, you would need to ask your admins to add an org level skill