Canonical specialist orchestration skill. Use proactively for substantial work that should be delegated, tracked, reviewed, fixed, tested, or merged through specialists: code review, debugging, implementation, planning, doc sync, security checks, multi-step…
xtrm-dev/specialists
SkillsMP has collected 8 skills from xtrm-dev/specialists. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 8
- GitHub stars
- 4
- GitHub forks
- 1
Skills in this repository
Showing 8 of 8 collected skills.
Use this skill when creating or fixing a specialist definition. It guides the agent through writing a valid `.specialist.json`, choosing supported models, validating against the schema, and avoiding common specialist authoring mistakes.
Reconcile specialists runtime drift and xtrm-managed asset drift across one repo or many. Use this skill when user says "update specialists", "specialists is out of date", "xtrm drift", "skills not updating", "assets out of date", or when operator needs…
Analyze specialist KPI data in observability SQLite. Use for runtime, payload, waiting, tool-call, and outlier analysis. Token estimates use cl100k_base-style approximation with ~±5% accuracy.
Use this skill for node-coordinator behavior. The coordinator is a CLI-native orchestrator that drives NodeSupervisor via `sp node` commands.
Operator-offline autonomous orchestration overlay. Activate when the user says "auto mode", "full auto", "run autonomously", "I'll leave you alone", or similar — and hands over a multi-item priority list. Layers on top of `using-specialists`: paranoid pacing,…
First-run setup workflow for a Specialists install. Use when the user says "setup specialists", "configure specialists", "change the specialist models", "models shipped do not exist on my machine", "set notes_mode globally", "opt out of GitNexus for one…
Use this skill for synchronous one-shot specialist invocations via `sp script` (CLI) or `sp serve` (HTTP daemon). These run READ_ONLY, template-driven specialists with `$var` substitution and return JSON in-process — no beads, no chains, no worktrees, no job…