The future will be AI or nothing at all.
Orbitant's plugin marketplace — skills, agents, and commands organized by vertical. Compatible with Claude Code, Claude.ai, and the Claude API.
Documentation: https://weorbitant.github.io/orbitant-os
# Add the marketplace
/plugin marketplace add weorbitant/orbitant-os
# Install what you need
/plugin install orbitant-marketing
/plugin install orbitant-chief-of-staff
/plugin install orbitant-business
# Update when there are new versions
/plugin update| Plugin | Version | Skills | Commands |
|---|---|---|---|
| orbitant-marketing | v1.1.0 | blog-post-review, blog-post-create, blog-post-translate, tone |
— |
| orbitant-chief-of-staff | v1.3.2 | graceful-degradation, goal-alignment, voice-drafting |
/preflight, /status, /today, /triage, /week, /prep, /crm |
| orbitant-business | v0.4.0 | — | /challenge, /highlight, /opportunity, /todo, /query, /preflight, /report |
- Claude Code — native plugin support
- Claude.ai — upload skills directly
- Cursor, Cline, Copilot — via skills.sh
- Claude API — programmatic access
# Install to other agents via skills.sh
npx skills add weorbitant/orbitant-os --skill orbitant-blog-post-review --agent cursor -yThis is useful when:
- You want to use skills outside of Claude Code's plugin system
- You're using a different AI coding agent
- You need to install skills in CI/CD pipelines
Use the /v1/skills endpoint. See Skills API docs.
Some plugins require MCP servers (e.g., Gmail, Calendar, Slack). Run the setup script to configure them:
# Community users — interactive plugin selection
./install.sh
# Orbitant team members — sets up everything
./install.sh --teamThe script checks prerequisites, registers MCP servers via claude mcp add, and guides you through OAuth authentication for each service.
orbitant-os/
├── .claude/
│ └── CLAUDE.md <- project instructions for Claude
├── .claude-plugin/
│ └── marketplace.json <- marketplace manifest
├── plugins/
│ ├── orbitant-marketing/
│ │ ├── .claude-plugin/
│ │ │ └── plugin.json
│ │ └── skills/
│ │ ├── blog-post-review/
│ │ ├── blog-post-create/
│ │ ├── blog-post-translate/
│ │ └── tone/
│ └── orbitant-chief-of-staff/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── skills/
│ ├── commands/
│ ├── agents/
│ ├── crm/
│ └── references/
├── .github/
│ ├── assets/ <- images and screenshots
│ ├── schemas/ <- JSON schemas for validation
│ └── workflows/
│ └── validate.yml <- CI pipeline
├── scripts/ <- validation scripts
├── .gitignore
├── CONTRIBUTING.md
├── FAQ.md
├── LICENSE
├── package.json
└── README.md
Each vertical is an independent plugin with its own namespace. This means:
- No collisions: Skills use prefixed names (e.g.,
orbitant-blog-post-review) so Claude can distinguish them from community skills. - Install only what you need: A marketer doesn't need infra skills, and vice versa.
| Component | What it is | How it triggers |
|---|---|---|
| Skills | Instructions Claude loads automatically when relevant | Claude reads the description and decides |
| Agents | Specialized sub-agents with restricted tools | Invoked via slash command or by another agent |
| Commands | Slash commands invoked manually | User types /orbitant-marketing:command-name |
- Create folder:
plugins/orbitant-{vertical}/skills/{skill-name}/ - Add
SKILL.mdwith frontmatter:
---
name: orbitant-{short-name} # ALWAYS prefix with orbitant-
description: |
What the skill does. When to activate it.
Be specific — this triggers Claude to load the skill.
version: "1.0.0"
license: MIT
metadata:
author: your-name
tags: comma, separated, tags
---- Update
marketplace.jsonand bump version inplugin.json - Open a PR
See Creating Skills for detailed guidelines.
# Install dependencies
npm install
# Run validation (same as CI)
npm run check
# Test plugins locally
claude --plugin-dir ./plugins/orbitant-marketing
# Website development
npm run website:dev # Dev server
npm run website:build # Build static siteFull documentation is available at https://weorbitant.github.io/orbitant-os
MIT — see LICENSE.