Publish to the Hub

Share your skills, tools, and agents with the Plexo community. Three ways to publish — pick the one that fits your workflow.

Publish a Skill

Create a SKILL.md file in your GitHub repo. Skills are procedural knowledge modules written in markdown with structured frontmatter.

---
name: my-skill
description: A short description of what this skill does
version: "1.0.0"
invocation: auto
tags: [automation, code]
author: your-name
---

## Instructions

Describe what the agent should do when this skill is invoked...

Install via URL: plexo install https://github.com/you/repo

Publish a Fabric Extension

For tools, channels, and MCP servers, create a plexo.json manifest. Extensions run as persistent workers with full lifecycle management.

{
  "plexo": "0.4.0",
  "name": "@your-org/my-tool",
  "type": "tool",
  "version": "1.0.0",
  "description": "What this tool does",
  "entry": "dist/index.js",
  "functions": [{ "name": "my_function", "description": "..." }]
}

Publish via API

Use the registry API to publish programmatically. Great for CI/CD pipelines and automated releases.

POST /api/v1/registry
Content-Type: application/json
X-User-Id: your-user-id

{
  "manifest": { ... },
  "displayName": "My Skill",
  "tags": ["automation"],
  "category": "automation",
  "readme": "# My Skill\n\nFull description...",
  "repositoryUrl": "https://github.com/you/repo"
}