Skills
Keep reusable workflows in files that e reads when the task calls for them.
On this page
Write a skill
Create a directory under ~/.e/skills/ with a SKILL.md inside. The name and description tell e when the workflow is relevant.
---
name: release
description: prepare a release of this repository
---
Run the release checks listed in the README.
Review the changelog against the diff.
Report failures before creating a tag.The model receives the name, description, and file path in its catalog. It reads the body with the ordinary read tool when the task matches, rather than carrying every workflow in context.
Choose when it loads
Type $ in the composer to pick a skill yourself. To make a skill available only through that picker, add disable-model-invocation: true to its frontmatter. It will stay out of the model catalog.
Descriptions can span multiple lines. e folds them into one line for the catalog and picker. Skill files are read when used, so updating a workflow does not require restarting e.
Personal, project, and package skills
Keep personal skills in ~/.e/skills/ and shared repository skills in .e/skills/. Project skills load only after directory trust. A project skill shadows a global skill with the same name; a global skill shadows a package skill.
Installed package skills appear with a Package label in the picker. See Packages to distribute a workflow with its prompts, extensions, or themes.
e docs skills