Mogplex Docs
Configure & Extend

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 are the currently-shipping path for letting an external agent reach a user's Mogplex capabilities. They are the drop-in substitute for the MCP server until that ships.

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

SkillRole
using-mogplex-cliUmbrella. Guides the user through the Mogplex cockpit when they ask for a workspace action.
mogplex-slashRecommends the right slash command for a user's intent.
mogplex-authWalks the user through the in-app login flow and credential troubleshooting.

The current Mogplex CLI is interactive-only — these are guidance skills that teach an agent to advise the user on cockpit workflows. They do not drive the TUI. When the MCP server ships, that path will give external agents direct programmatic access to Mogplex capabilities without going through the cockpit.

Why this is the right path today

  • 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 (today)MCP server (preview)
StatusAvailablePreview design; not live
ProtocolSkill file (guidance)MCP Streamable HTTP
AuthIn-app login → ~/.mogplex/auth.jsonOAuth 2.1 + PKCE (DCR)
Token pasted in config?NoNo
Execution pathAgent advises user; user drives the cockpitExternal agent calls MCP tool directly
Streaming progressn/a — user watches the cockpitMCP notifications/progress
Host requirementSkill-aware (Claude Code, Agent SDK, Cursor rules)Remote-MCP-aware with OAuth
Host reach todayHighClaude Code ≥ latest, Cursor, a few others

When the MCP server ships, it becomes the right path for hosts that need programmatic access without involving the user. Skills will continue to be useful for hosts that don't speak remote MCP and for situations where the user is the right one 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-skills

Then 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

Edit on GitHub

On this page