The workspace
Skills
A skill is a plain instruction pack, the same shape Claude Code and Codex already use. Install one and it rides along with the task, so you never have to restate your standards at the top of every chat.
Teach it once
Your tone, your review checklist and your house rules, written down a single time and applied by whichever models run the work.
A library you can browse
Install curated skills from the Marketplace, import one from a repository, or write your own in the editor.
Portable by design
Skills are ordinary instruction files, so one written for another tool works here and one written here works there.
How it works
- 01
Find one or write one
Browse the library, import from a repository, or start from a blank editor.
- 02
Install it
It joins your shelf and is offered from the composer whenever it is relevant.
- 03
Publish it, if you like
Share a skill to the Community and other people install it unchanged.
Try asking
Write me a skill that reviews pull requests the way our team does.
Turn our brand style guide into a skill and apply it to this draft.
Use my code review skill on this diff and tell me what it flags.
Questions
- How is a skill different from a plugin?
- A skill is knowledge injected into the model; a plugin is a capability the app gains. A skill teaches Alias how you want something done, a plugin gives it a new thing it is able to do.
- Do I need to write code?
- No. A skill is a Markdown instruction file. If you can describe in writing how you want something done, you can write one.
- Does a skill run on every message?
- Only when it is relevant to the task. You can also pin one to a session from the composer when you want it applied to everything you are about to ask.