Package how to do something as a skill that the agent reads in only when needed — use the built-in ones, or write and import your own.

A skill packages a way of doing something for the agent: normally only its name and a one-line description are in view, and the full instructions are read in only when it's used.

Skills vs rules

	Rules	Skills
When it enters the context	Every turn	Only when used
How it's triggered	Automatically	The agent calls it when it matches, or you call it with `/<name>`
Best for	Project-wide conventions	How to do one specific thing

Anything that should always apply goes in a rule; anything needed only for a particular job becomes a skill.

Built-in skills

Skill	Use
Code Review (`/review`, `/cr`)	Review code changes; see Review
Web page	Single-file web pages / landing pages that open directly
Mini game	Single-file HTML games
Animation	Loading animations, icon motion, explainer animations
Data chart	Turn data into an interactive web chart or a PNG
Video	A time-keyed web animation exported to MP4
PPT deck writer	Build a longer deck slide by slide and export it
Web data extraction	Pull and tally data from web pages / admin panels
UI testing	Visual, responsive, accessibility and interaction tests for web pages
Knowledge ingest	Turn documents and links into knowledge base cards

Writing your own

Each skill is a folder containing a SKILL.md:

.neox/skills/
  deploy-staging/
    SKILL.md
    scripts/check.sh      ← optional scripts or reference files

SKILL.md starts with frontmatter, followed by the instructions for the agent:

---
name: deploy-staging
description: Deploy the current branch to staging and verify it
neox:
  aliases: [ds]
  allowedTools: [execute_shell, web_fetch]
---

1. Confirm `pnpm build` passes
2. Push to staging
3. Poll the health-check endpoint
4. Fetch the homepage; confirm a 200 and the key elements

Field	Required	Meaning
`name`	✓	Skill name
`description`	✓	One-line summary; the agent uses it to decide when to use the skill
`neox.aliases`		Aliases, callable as `/<alias>`
`neox.allowedTools`		Tells the agent to use only these tools while running the skill (a prompt instruction, not a hard block)
`paths`		File patterns; the skill is enabled only when matching files are touched
`user-invocable`		Set to `false` to hide it from the slash menu

Make description say when to use it, so the agent picks it up at the right moment.

Where skills live

Location	Scope
`~/.neox/skills/<name>/`	All projects
`<project>/.neox/skills/<name>/`	This project only
Skills bundled with enabled plugins	Follow the plugin's enabled state

Edits are picked up automatically, no restart needed.

Installing other people's skills

Desktop — Settings → Agent → Skills: import from a URL or a local folder, or import skills you already have in ~/.claude/skills / ~/.codex/skills in one click
CLI — /skills opens a menu: list, import, create, manage (trust / update / uninstall), refresh
By hand — copy the skill folder into one of the directories above

Using a skill

Usually you don't have to: say "deploy to staging" and the agent calls the skill when the description matches. To name it explicitly, type /deploy-staging (or the alias /ds) in the input box, optionally followed by arguments.

Availability

	Supported
Desktop	✓
CLI	✓