Skills and plugins

Use skills for repeatable work

A skill is a reusable workflow that guides EvoX through a particular task and preserves a consistent process and quality bar.

Skills work best when a task already has a stable, repeatable method, such as weekly briefs, document reviews, presentations, charts, or writing results into another system.

Validate a working method first

Start with a bounded recurring task. Check for stable inputs, reusable steps, and a clear result before turning it into a skill.

1. Define goals and material

   Choose recurring work and specify input scope and deliverables.

2. Set acceptance criteria

   For example, retain sources and report missing evidence rather than inventing facts.

3. Try and inspect the outcome

   Use new material to check reusable steps instead of copying the previous answer.

4. Then manage configuration

   Save a skill for lasting reuse; Skill management covers import, dependencies, and activation.

Use plugins to connect tools and share workflows

Plugins bring tools into tasks; skills explain how to organize their use. Installation, account connection, and action authorization remain separate.

Plugins

Plugins provide their declared capabilities. Check whether tools support the operation rather than inferring full application control from a plugin name.

Apps

Account-based apps access resources authorized for that account. Sending, deleting, and publishing must still follow the current task scope.

Skills directory

The skill catalog helps locate existing methods. Configuration owns import and activation; tasks need explicit inputs and outputs, followed by evidence that the skill was used.

Use subagents for specialized work

Subagents are helper agents with specialized responsibilities, context, or tool scope. Add them from the local agent directory so EvoX can delegate suitable subtasks.

Use subagents when work can genuinely run independently or needs distinct expertise, and define each agent's inputs, outputs, and permissions.

Use Hooks for lifecycle events

Hooks run commands at lifecycle events and suit deterministic checks, logging, and notifications. This differs from selecting skills based on task content.

Automatic triggers still need boundaries: inspect command sources, working directories, data access, and failure handling. An event trigger is not unlimited authorization.

Choose a skill or a plugin

Use skills for repeatable methods and plugins for external tools. Continue with Skill workflows to design and validate methods, or Plugins to invoke tools and check results.