Vibes & Skills
Create reusable checkpoint definitions and manage the skill packages that guide workers and independent reviewers in a Vibe Lane.
Open the Vibes library
- Open Automation from the application side menu.
- Select the Vibes tab.
You can author Vibes without an open VibeSpace. Each Vibe is a reusable, versioned definition that can be placed in multiple Vibe Lanes. The library shows each Vibe’s Ready or Needs setup status and how many lanes use it.
Create a Vibe
- In the Vibes tab, select New Vibe.
- Choose an existing category, or use the adjacent add control to create one with a custom name and icon.
- Define the expected outcome and working instructions.
- Assign any Work skills the worker should follow.
- Write the done-when criteria.
- Assign any Review skills the independent reviewer should follow.
- Under Verified by, choose Reviewer agent or You.
- Set the attempt and time limits.
- Choose whether exhausted limits Stop or Ask to steer.
- Configure any checkpoint execution settings you want to override.
- Select Save Vibe.
A Vibe contains five areas:
| Area | What you define |
|---|---|
| Category | Where the Vibe appears in the library and Vibe Lane designer. |
| Outcome | The goal, working instructions, and Work skills. |
| Done when | Pass criteria, Review skills, and who verifies the result. |
| Limits | Maximum attempts, time limit, and whether exhaustion stops or asks for steering. |
| Execution | Optional agent, model, mode, and reasoning settings. |
Category and status filters can be combined. Category labels also distinguish Vibes that intentionally share a short name, such as Implement or Verify.
Choose execution settings
Execution settings belong to a Vibe’s checkpoint rather than the task creation screen. Leave a setting at its default to inherit ACP behavior.
| Setting | Default behavior |
|---|---|
| Agent | Uses the app-wide ACP agent. |
| Model | Uses the app-wide model when Agent is inherited. If you select another agent and leave Model at Agent default, that agent chooses its own model. |
| Mode | Uses the selected agent’s default mode. |
| Reasoning | Uses the app-wide ACP reasoning default. |
Model and mode choices are scoped to the selected agent. Some agents load their available options when you select them; reasoning controls appear only for agents that expose them.
Vibe Lane execution always uses Full Trust. Trust is not an inheritable or configurable Vibe setting.
Understand versions
Saving edits to a Vibe creates a new version. Existing Vibe Lanes remain pinned to the version they already use and do not change automatically.
When a lane’s Vibe has a newer version:
- Open the Vibe Lane editor.
- Find the step with an available update.
- Choose Use latest.
- Save the lane.
The lane now pins the selected Vibe version for new tasks. Tasks that already started keep the exact lane version they began with.
You can delete a Vibe only when no Vibe Lane uses it.
Resolve Needs setup
A Vibe marked Needs setup remains visible in the library but cannot be added to a Vibe Lane. Complete its missing or invalid definition before assigning it to a lane.
If a Vibe depends on a skill that becomes unavailable, resolve that skill’s requirements before starting new work.
Open the Skills library
- Open Automation.
- Select the Skills tab.
A skill is a reusable package rooted at SKILL.md. Supporting content is optional:
| Package content | Purpose |
|---|---|
SKILL.md | Required entrypoint containing the skill instructions. |
| References and templates | Supporting guidance and reusable source material. |
| Scripts | Commands or automation used by the skill. |
| Assets | Files the skill needs while working. |
| Agent metadata | Additional package information for agent use. |
Understand skill package types
| Type | Source and editing behavior |
|---|---|
| Bundled | Ships with CrispyVibe and is read-only. |
| Personal | Created and edited in CrispyVibe. |
| Linked | Remains in an external folder and is read-only in CrispyVibe. |
Linked packages use their files at the external location, so changes made there affect what CrispyVibe reads. Duplicate a linked package when you need a stable, editable personal copy.
Import Skills
You can link one skill or discover many packages inside a larger folder.
- Select Import Skills in the Skills library.
- Choose a
SKILL.mdfile, a single package folder, or a repository containing nested skill packages. - Select Import Skills in the file dialog.
CrispyVibe discovers packages recursively and adds them as Linked skills. Linked sources stay in their external location; CrispyVibe does not copy them. Each discovered package must have its own SKILL.md entrypoint.
💡 Tip: To copy packages into CrispyVibe instead of linking them, use crispy skill import, which copies by default. You can also duplicate a linked skill to get a stable Personal copy.
Duplicate a skill
Bundled and linked skills are read-only. Duplicate one to create an editable Personal package.
- Select a Bundled or Linked skill.
- Select Duplicate.
- Open the new Personal package.
- Edit its instructions or supporting files.
Duplication preserves the complete package, including its supporting references, scripts, assets, templates, and metadata.
Delete or unlink a skill
Select Delete Skill to remove a Personal package, or Unlink Skill to remove a Linked package from CrispyVibe without touching its external folder. Bundled skills cannot be removed.
You cannot delete or unlink a skill while a Vibe uses it. Remove the skill from those Vibes first.
Assign Work and Review roles
The Skills library shows whether a package can be used for Work, Review, or both.
| Role | How the skill is used |
|---|---|
| Work | Guides the worker that produces or changes the outcome. |
| Review | Guides only the independent reviewer that checks the result against the done-when criteria. |
Review skills are not sent to the worker. They are useful for reusable procedures such as code review, security review, or semantic-version validation.
Interactive skills can guide Work, but they cannot be assigned to the unattended independent reviewer. Use an unattended Review-ready skill for agent verification, or configure the Vibe as Verified by: You when a person must interact with the review process.
Check readiness and requirements
The Skills library shows each package’s roles, interaction mode, resources, required commands, and readiness.
A skill is unavailable for new Vibe assignments when a referenced local file is missing or a required command is not installed. Before a task starts its first attempt, CrispyVibe also confirms that each assigned package still contains a readable SKILL.md.
To resolve an unavailable skill:
- Open the skill.
- Select its Requirements tab.
- Identify the missing command or package file.
- Install the required command or restore the referenced file.
- Confirm that the skill reports ready before assigning it to a Vibe.
Readiness confirms package structure and declared commands. It does not sandbox the package or guarantee that its scripts and instructions are safe, so review imported packages before using them.
Manage Vibes and Skills from the CLI
Agents and scripts can list, validate, and change Skills and Vibes with crispy skill and crispy vibe. These commands use the same readiness checks and versioning as the app: Vibe updates and deletes require the current version, and Skill removal is refused while a Vibe uses the Skill. Definitions are global to the app, not to one project.