portable-skill-18

Provides a minimal portable skill definition for agent plugin testing.

2.7k|171|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/compozy/compozy --skill portable-skill-18
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: portable-skill-18
Source: https://github.com/compozy/compozy/tree/main/internal/extension/testdata/agent-plugin-30-skills/skills/portable-skill-18
Command: npx skills add https://github.com/compozy/compozy --skill portable-skill-18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill serves as a minimal, self-contained portable skill definition used to verify that agent plugins can discover and load skills from a skills directory.

Core Features & Use Cases

  • Portable Skill Definition: Defines a standalone skill with only a SKILL.md entry point and YAML frontmatter.
  • Plugin Loading Validation: Acts as test fixture data for validating skill discovery in the Compozy extension system.
  • Use Case: When developing or testing an agent plugin that bundles multiple skills, this unit confirms the loader correctly parses skill name and description metadata.

Quick Start

Ask the agent to use portable skill 18 to confirm the skill loads and responds.

Frequently Asked Questions about portable-skill-18

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

FAQPage Schema
What makes a valid skill unit for an agent plugin?

A valid skill unit is a directory containing a SKILL.md file at its root with YAML frontmatter defining at least a name and description. Optional scripts, references, and assets directories can provide additional resources.

How do I test skill loading in a Compozy agent plugin?

Place skill directories with valid SKILL.md files under the plugin's skills folder and run the extension loader. Fixture skills like this one confirm that discovery and frontmatter parsing work correctly.

Does a skill require scripts or references directories?

No, scripts, references, and assets directories are optional. A skill only requires a SKILL.md file with name and description frontmatter to be discovered and loaded.

Why is my skill not being discovered by the plugin?

Discovery fails when SKILL.md is missing, misnamed, or lacks required frontmatter fields. Verify the file sits at the skill directory root and defines both name and description in valid YAML.