Skills
Skills extend fx with reusable instructions for tasks and workflows. fx can choose a relevant skill for your prompt, or you can select one yourself.
Browse and invoke
Browse available skills:
/skillsSearch by name or filter by source. Press enter to add a skill to your prompt, then describe what you need. You can also type $ to open the skill picker. Both match a name by each word and by its letters in order, so fxcommit finds fx-commit.
For a skill named review-tests:
$review-tests Review the tests changed in this branch.
fx loads the selected skill's full instructions when you send the prompt and sends them with that turn. Later turns send that turn as it was sent, instructions included.
You can also name a skill at the start of a prompt, as in Use the review-tests skill to check this branch. fx doesn't select a skill named inside quotes or code, or one you tell it not to use, as in don't use $review-tests.
Find a specific skill:
/skills show <name>If several skills have the same name, typing $name loads none of them. Select the one you want in /skills or the $ picker, which show each skill's source.
Install
Install one skill from a repository:
/skills install vercel-labs/skills --skill find-skillsInstall from a local directory:
/skills install ./review-testsA source can also be a Git URL, a skills.sh page, owner/repo@skill, or an npx skills add command. /skills add works the same as /skills install.
Installed skills go to ~/.fx/skills/. Use --skill to choose one from a repository; omit it to install all skills in the source. Installing a skill that's already there replaces it.
You can also ask fx to install a skill. fx uses the install_skill tool for that request, and for an npx skills add command the model runs. The tool needs approval under your permission rules. /skills path shows where fx stores installed skills.
Create a skill
Create a template:
/skills create review-testsOpen ~/.fx/skills/review-tests/SKILL.md in your editor and replace the template with instructions for the task. Running /skills create again for the same name replaces that file with a new template. For a skill shared with your project, create .fx/skills/review-tests/SKILL.md in the repository instead.
For example:
---
name: review-tests
description: Review tests for missing cases and brittle assertions.
---
# Review tests
- Read the changed code and its tests.
- Find missing cases and assertions tied to incidental output.
- Report findings with file paths. Edit files only when asked.
fx checks for new and changed skills each time you send a prompt or run /skills, so you can use your skill in your next prompt.
File format
Include a name in the YAML header. Use description to explain when fx should use the skill, and write the instructions below the header. Without a header, fx uses the directory name. A header without a name is a discovery issue, and fx doesn't load the skill.
Remove an installed skill
/skills remove review-testsThis removes the skill from ~/.fx/skills/. Remove workspace or third-party skills at their source. The /skills catalog shows each skill's source.
Discovery roots
fx checks .fx/skills/, skills/, and compatible directories from the workspace upward, stopping before your home directory:
.fx/skills/
skills/
.opencode/skills/
.codex/skills/
.claude/skills/
.agents/skills/
.claw/skills/
It then checks user roots:
~/.fx/skills/
~/.config/opencode/skills/
~/.codex/skills/
~/.claude/skills/
~/.agents/skills/
~/.claw/skills/
Additional workspace directories do not contribute skills.
fx doesn't follow symbolic links in ~/.fx/skills/. In the other roots, a skill folder can be a symbolic link, and fx loads it when the link resolves inside the folder that holds the root, such as the workspace or your home folder. To allow links to other places, list those directories in skill_symlink_authorities in ~/.fx/settings.json, as up to 32 absolute paths without ..:
{
"skill_symlink_authorities": ["/Users/example/shared-skills"]
}
Skills that fx can't load, such as a link outside these places or a SKILL.md it can't read, are listed as discovery issues in Full detail, which ctrl+o opens.