Skills guide the AI agent, but you still stay in control. Review the plan before the agent runs, and review the diff before keeping changes.
Why use Neo Skills?
Create with a recipe
Scaffold a Flutter app with Neo, or add Neo to an existing app, from the official install steps.
Update with context
Give the agent a workflow that starts from Neo’s official docs and release notes.
Keep changes reviewable
Skills confirm a plan first and leave focused edits you can inspect before accepting.
Built for the future
Skills are how Neo can ship higher-level AI workflows as the framework grows.
Install
Install Neo Skills with the skills CLI:Terminal
Available skills
create-neo-project
Use create-neo-project to create a Flutter app with Neo, or to add Neo to an existing Flutter project. The skill detects the folder you are in, shows a plan, and waits for confirmation before it writes anything.
It handles three situations:
- Empty folder — creates the Flutter project in place, then installs Neo.
- Projects root — creates a new project folder, then installs Neo.
- Existing Flutter app — adds Neo and migrates the app shell without replacing your screens.
update-neo instead.
update-neo
Use update-neo when you want an agent to upgrade the neo Flutter package in an app and help migrate the project across the versions you cross.
How to use create-neo-project
1
Open the target folder
Use an empty directory, a folder of apps, or an existing Flutter project. Do not run it inside the Neo framework checkout unless you name a different target path.
2
Run the skill
Use
/create-neo-project to start the setup workflow.3
Confirm the plan
The agent lists the mode, path, commands, and files it will change. Approve before it executes.
4
Review the result
Check the diff, run the app, and keep only the changes that match your project.
Example prompts
How to use update-neo
1
Open your Flutter project
Start from the app or package that depends on
neo.2
Run the skill
Use
/update-neo to start the Neo update workflow.3
Review the result
Check the diff, run your normal verification, and keep only the changes that match your project.
Example prompts

