Evose
BuildCapabilities

Skills

Reusable "experience packs" · SKILL.md spec · Workspace vs Organization

A Skill is a reusable experience pack: bundle a set of prompts + scripts + reference materials, shared across multiple Agents / Workflows.

Skill ≠ Tool:

ToolSkill
FormRemote RPCStatic asset bundle
ContentOne or more callable methodsPrompts / templates / scripts / files
Example"Query weather API""Company-style writing guide"
InvocationLLM function callInjected into the prompt or referenced from code

Skill Shape

A Skill = a directory + SKILL.md:

my-skill/
├── SKILL.md                # Metadata (required)
├── prompt.md               # Main prompt
├── examples/               # Examples
│   ├── good.md
│   └── bad.md
└── templates/
    └── output-template.md

SKILL.md describes the Skill:

---
name: Company Writing Guide
description: Rewrite any input text into the company's standard format
tags: [writing, guideline]
---
 
# How to Use
...

Aligned with Anthropic Agent Skills

Evose's Skill format is compatible with Anthropic's Agent Skills. Existing Skills can be imported directly.

Create a Skill · Two Modes

Mode 1 · Direct UI

Workspace → Capabilities · SkillNew → fill the form:

FieldDescription
Icon / name / descriptionMetadata
ContentMarkdown editor; attachments supported
TagsFor categorization and search

Mode 2 · Import

Pack an existing Skill directory into a ZIP and upload, or pick a local directory (Private). The system auto-scans SKILL.md.

Import Constraints

ConstraintLimit
Top-level Skill directories≥ 1
SKILL.md locationRoot or one-level subdirectory (one or the other; cannot coexist; cannot go deeper)
File count per SkillConfigurable in org settings
Total size per SkillConfigurable in org settings
Binary file sizePer-file limit configurable in org settings

Lifecycle

[New] → Draft (default, not callable)
   ↓ publish
   Live (referenceable by Agent / Workflow)
   ↓ unpublish / delete
   Unpublished (calls from existing references will fail)
   Deleted (permanent, irreversible)

Workspace Skill vs Organization Skill

Workspace SkillOrganization Skill
CreatorWorkspace admin / app builderOrg admin
Best forTeam-private experiments, project-specific guidesCompany-wide standards (writing style, review rules, translation guides)
AuthorizationVisible only in this workspaceGranted to specified workspaces

Organization skill management

Reference a Skill in Agent / Workflow

Agent

Edit Agent → Skills tab → tick the Skills you want to use. The selected Skills' prompt.md content is injected into the role prompt.

Workflow

In an LLM node → Load Skill → select → auto-injected.

A Real Example

Scenario: every Agent in the company must follow the same customer-service script guide.

Org Skill: CS Script Guide v2
├── SKILL.md
├── prompt.md      # Salutations, tone, banned-word list
├── examples/      # 6 good/bad pairs
└── templates/     # Templates for satisfied / dissatisfied scenarios

Each workspace's CS Agent ticks this Skill uniformly → company-wide consistent CS scripts; versioning and rollouts are easy.

Anti-Patterns

  • Stuffing a whole business process into a Skill — that's Workflow's job
  • Putting volatile data (product prices) into Skill content — use a knowledge base
  • Cramming 100 use cases into one Skill — split into focused Skills

Next Steps

On this page