exo:agent-skills

Load Exo agent skills from local and GitHub sources via SkillRegistry.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/midsphere-ai/exo --skill exo-agent-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exo:agent-skills
Source: https://github.com/midsphere-ai/exo/tree/main/skills/agent-skills
Command: npx skills add https://github.com/midsphere-ai/exo --skill exo-agent-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables developers to implement and manage Exo agent skills by providing clear front-matter schemas, loading mechanisms, and tooling mappings that power runtime agents.

Core Features & Use Cases

  • Create skill files that Exo agents consume at runtime (skill.md or SKILL.md) with YAML front-matter for name, description, type, active, and tool_list.
  • Load skills from local disk or GitHub repositories using SkillRegistry, enabling multi-source composition and conflict resolution.
  • Wire skills into agents by mapping metadata to actual tools and building instruction prompts for orchestration agents.

Quick Start

Create a skills/agent-skills/skill.md with YAML front-matter including name and description and a Markdown body describing usage.

Frequently Asked Questions about exo:agent-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define Exo agent skills with YAML front-matter for runtime consumption?

Exo agent skills are defined by creating a skill.md file with YAML front-matter specifying name, description, type, active, and tool_list, followed by a Markdown body describing usage instructions for runtime consumption.

Can I load Exo skills from both local disk and GitHub repositories?

Yes, you can load Exo skills from both local disk and GitHub repositories using SkillRegistry, which enables multi-source composition and handles conflict resolution when discovering and loading skill metadata across different sources.

How do I map Exo skill metadata to agent tools and build instruction prompts?

You map Exo skill metadata to agent tools by using the tool_list field within the skill's front-matter, wiring the defined metadata to actual tools and generating instruction prompts that orchestrate runtime agent workflows.

What is the best way to resolve conflicts when loading multiple Exo agent skills?

The best way to resolve conflicts when loading multiple Exo agent skills is to use SkillRegistry, which provides built-in conflict resolution mechanisms to manage overlapping skill definitions during multi-source discovery and loading operations.

Does the Exo skill registry enforce front-matter parsing for skill discovery and search?

Yes, the Exo skill registry enforces front-matter parsing to validate skill files during discovery and search operations, ensuring that required metadata fields like name and description are correctly extracted for agent tool mapping.