Skills
Anthropic Agent Skills that teach Claude Code, the Claude Agent SDK, Cursor, opencode, and other skill-aware hosts how to drive a user's Mogplex workspace through the `mogplex` CLI. Available today.
Skills teach an external agent how to guide a user through Mogplex CLI workflows. For direct programmatic access to Mogplex, install the live Mogplex MCP instead.
The canonical skill files and the per-skill reference pages live under CLI → Skills. This page is the entry point from the Extend section — it describes the shape of the set and the trade-offs versus MCP. Go to /cli/skills for the individual skills.
What the set covers
| Skill | Role |
|---|---|
using-mogplex-cli | Umbrella. Guides the user through the Mogplex cockpit when they ask for a workspace action. |
mogplex-slash | Recommends the right slash command for a user's intent. |
mogplex-auth | Walks the user through the in-app login flow and credential troubleshooting. |
These are guidance skills that teach an agent to advise the user on cockpit workflows. They do not drive the TUI. Mogplex MCP gives external agents direct programmatic access without going through the cockpit.
Why use skills
- No pasted tokens. The cockpit's in-app login flow owns the credential and writes it to
~/.mogplex/auth.json— see the Authentication guide for precedence rules and file contents. The external agent never sees raw auth material. - Works in every skill-aware host. The skill format is portable: Claude Code, Claude Agent SDK, and any host that reads
SKILL.md-style files. Cursor project rules work too by copying the skill body. - Thin wrapper. Skills do not duplicate Mogplex logic — they are instructions for how the user should drive the CLI cockpit, which talks to the existing Mogplex runtime.
- No infra dependency. Ships the moment the CLI is on the user's
PATH. Nothing to deploy, no tokens to provision.
Skills vs MCP server at a glance
| Skills | MCP server | |
|---|---|---|
| Status | Available | Available |
| Protocol | Skill file (guidance) | MCP Streamable HTTP |
| Auth | In-app login → ~/.mogplex/auth.json | OAuth 2.1 + PKCE (DCR) |
| Token pasted in config? | No | No |
| Execution path | Agent advises user; user drives the cockpit | External agent calls MCP tool directly |
| Progress | User watches the cockpit | Agent reads run and automation logs on demand |
| Host requirement | Skill-aware (Claude Code, Agent SDK, Cursor rules) | Remote-MCP-aware with OAuth |
| Host reach today | High | Claude Code ≥ latest, Cursor, a few others |
Use MCP when a host needs programmatic access without involving the user. Use skills when the host does not speak remote MCP or the user is the right person to drive the cockpit.
Install
The skills live in webrenew/mogplex-docs under skills/. Pick one fetch method, which sets a SKILLS path variable used by the copy step below:
# Option A — full clone (gives you the rest of the docs repo too)
git clone https://github.com/webrenew/mogplex-docs.git
SKILLS=mogplex-docs/skills
# Option B — sparse download of just the skills/ tree
# degit copies the *contents* of skills/ into mogplex-skills/,
# so mogplex-skills is the skills tree (no nested skills/ dir).
npx -y degit webrenew/mogplex-docs/skills mogplex-skills
SKILLS=mogplex-skillsThen copy into your agent host. Both commands run from the same shell where you set $SKILLS:
# Global (Claude Code)
mkdir -p ~/.claude/skills && cp -R "$SKILLS"/* ~/.claude/skills/
# Or per-project (run from your project root)
mkdir -p .claude/skills && cp -R "$SKILLS"/* .claude/skills/See CLI → Skills for Agent SDK integration, Cursor instructions, and the full install matrix.
See also
- CLI → Skills — canonical reference for every skill
- Mogplex MCP — direct programmatic access to Mogplex
- Extend overview — the decision between Skills and MCP