Core Features
Skills
Paradev abilities your coding agents get automatically. Orchestration, automations, feedback, diagnostics, and more
Skills teach the coding agents you already use how to drive Paradev: orchestrate parallel agents, create automations, diagnose problems, and more.
Installation
Using the Paradev desktop app? Skills are already installed. The app provisions them at launch and keeps them updated.
Otherwise, install them directly:
npx skills add paradevai/skillsOr, in Claude Code, via the plugin marketplace:
/plugin marketplace add paradevai/paradevWhat You Get
| Skill | What it does |
|---|---|
superset:setup | Makes a repo Paradev-ready: authors .superset/config.json and project lifecycle scripts, then verifies with a real workspace |
superset:orchestrate | Turns the agent you're talking to into a coordinator of parallel agents; see Agent Orchestration |
superset:automate | Turns a recurring chore into an automation that runs on a schedule or an event, and reviews its first run with you |
superset:page | Builds and publishes shareable Pages, then updates them in response to pinned team comments |
superset:browser | Drives a workspace's in-app browser panes: open, navigate, screenshot, eval, read console, and raw CDP for click/type automation, and routes to Browser Use 3.0 for browsers the panes can't reach |
superset:computer | Drives native desktop apps through an accessibility-first driver (Cua Driver by default): inspect windows, click, type, use menus, and verify results with background interaction when the platform supports it |
superset:panes | Arranges a workspace's tabs and split panes in the desktop app: split, open tabs, resize, swap, move, focus, and close, with commands running in the new panes; see the panes CLI reference |
superset:standup | Sweeps your workspaces, tasks, and agent terminals into a digest: what needs you, what's in flight, what's blocked |
superset:doctor | Diagnoses Paradev problems (expired auth, offline hosts, stale versions) and fixes them one step at a time |
superset:feedback | Files a bug report or feature request: privately to the Paradev team (from your account, so we can reply) or as a public GitHub issue |
superset:10x | Audits how you use Paradev and teaches the advanced features you're not using yet |
superset:contribute | Sets up a Paradev open-source contribution end to end, following the repo's contribution rules |
Using Skills
You usually don't invoke them; agents pick the right skill from context:
- "report this bug to the superset team" →
superset:feedback - "what did my agents do overnight?" →
superset:standup - "run these three refactors in parallel" →
superset:orchestrate - "open localhost:3000 and click through the signup flow" →
superset:browser - "open the desktop app and change its settings" →
superset:computer - "split this and run the tests on the right" →
superset:panes
To invoke one explicitly: /superset:feedback in Claude Code, or /superset/feedback in the in-app chat. Other agents that read skills (Codex, Kimi, Vibe, Grok) see the same skills with a superset- prefix.
How They're Delivered
At launch, the desktop app writes managed copies into the standard discovery locations: ~/.claude/skills/superset/ (loaded by Claude Code as a plugin, hence the superset: namespace), ~/.agents/skills/, and ~/.agents/commands/.
- Your files are never touched. Managed files carry a marker; a skill or command you authored at the same path is left alone.
- Updates are automatic. Managed skills refresh on every app launch, and ones that no longer ship are cleaned up.