skills

Route broad or mixed Solo and SoloTerm requests across focused project, process, agent, durable-state, and automation skills. Use when choosing among Solo skills, deciding between one agent and an orchestrated cohort, learning Solo, or handling several Solo capabilities in one task. Do not use for non-Solo work, or when one clearly scoped Solo action already maps to a single focused skill.

Conduct and synthesize deep, exhaustive, comparative, or cross-checked research into a decision or contested question using independent evidence lanes, claim-level citations, contradiction resolution, and stress-tested conclusions. Use when the deliverable is a cited research synthesis or recommendation, including deep multi-source Stellar-ecosystem investigations. Do not use for a narrow lookup or single-source read — one fact, version, API signature, or docs page, even a Stellar or Soroban one; answer those directly from the authoritative source. Do not use for implementation, code review, or generic multi-agent coordination.

Plan and coordinate multi-agent work through Solo with bounded workers, durable state, locks, timers, evidence review, and handoffs. Use for parallel research, disjoint implementation lanes, cross-model review, cross-project cohorts, or delegation through several Solo agents. Do not use solely because research is deep or cited—citation and synthesis discipline come from a research method, not from orchestration—nor for single-agent, sequential, or shared-file work.

Configure, health-check, launch, prompt, inspect, resume, summarize, follow up with, and close one Solo-managed agent session. Use for built-in or custom CLI agent setup, launchability, one-off flags, input, output, status, summaries, idle or blocked handling, and owned-agent cleanup. Do not use for multi-agent orchestration or non-Solo agents.

Use agent-browser with Chrome DevTools Protocol virtual WebAuthn authenticators to test passkey, WebAuthn, Stellar smart account, wallet creation, wallet restore, and browser signing flows. Trigger when a task mentions passkeys, WebAuthn, virtual authenticators, Stellar Smart Account Kit browser tests, or agent-browser passkey automation. Do not use for browser flows without a passkey or WebAuthn ceremony—password logins and extension-wallet connects route to agent-browser alone.

Operate Solo-managed commands and terminals through start, stop, restart, rename, spawn, input, bulk actions, trust gates, auto-start, crash restart, and file-watch restart. Use when launching a dev stack, controlling project commands, renaming a process, opening terminals, sending input, or configuring restart behavior. Do not use for read-only status and readiness, project or solo.yml setup, or failure diagnosis.

Create, inspect, update, delete, fill, and export global or project Solo prompt templates with reusable placeholders. Use when saving recurring prompts, standardizing worker briefs or handoffs across agent tools, managing template scope, or backing templates up as Markdown. Do not use for current task state or durable project decisions.

Create and maintain project-scoped Solo todos with status, priority, tags, blockers, comments, locks, completion, and cross-project transfer. Use when turning plans into tasks, finding ready work, claiming todos, recording progress or handoffs, updating dependencies, or completing work. Do not use for narrative context, which belongs in scratchpads, or for controlling processes.

Automate and integrate Solo through MCP, CLI, local HTTP API, hosted API v1, documentation resources, prompts, and solo:// deep links. Use when scripting Solo, discovering live schemas, configuring MCP clients, consuming Solo docs programmatically, or choosing an integration surface. Do not use for normal interactive Solo work already owned by a focused skill.

Reconcile a finished Solo run across scratchpads, todos, timers, locks, and run-scoped KV, then retire the ephemeral copies without losing genuinely incomplete work. Promote only uncaptured durable conclusions into the repository's existing canonical docs first (ordinary completed-work history stays in Git), then archive scratchpads and complete or backlog todos. Use when wrapping up or closing out a finished run whose residue spans two or more of those state surfaces. Triggers: "close out this run", "wrap up and clean up this run", "promote this before we forget". Do not use for single-surface cleanup — creating or editing active scratchpads (solo-keep-scratchpads), maintaining the live actionable todo graph (solo-track-todos), or any single owning skill's own tidying — nor for any process control (that stays with solo-run-processes). This skill decides what is done, files it durably, and clears only the ephemeral copy.

Customize Solo workspaces, windows, sidebar, navigation, command palette, keymaps, appearance, external tools, notifications, account display, and updates. Use when organizing or personalizing Solo's app-level workspace experience. Do not use for repository or solo.yml changes, process lifecycle, or agent work.

Create and maintain project-scoped Solo scratchpads with revisions, structured Markdown, search, tags, archive, transfer, and import/export. Use for working plans, research, decisions, evidence, commands, summaries, and cross-agent handoffs — persistent across sessions but non-canonical; promote conclusions worth keeping to repository docs. Do not use for actionable owned work with status and blockers, which belongs in todos, or for reusable prompt text.

Inspect Solo-managed service status, terminal output, resource use, subprocesses, bound ports, localhost URLs, and startup readiness. Use when checking what is running, whether a server is ready, recent logs, stale status, URLs, ports, CPU, or memory without changing runtime. Do not use to change process lifecycle, edit configuration, or repair failures.

Configure and import Solo projects and shared solo.yml command stacks. Use when adding repositories, defining commands, working directories, environment values, execution profiles, auto-start or restart policy, YAML sync, command storage, or trust review. Do not use for personal workspace UI, runtime process control, or failure diagnosis.

Diagnose Solo project, command, terminal, service, CLI, shell, version-manager, trust, solo.yml sync, working-directory, execution-profile, WSL, restart-loop, output, port, and readiness failures. Use when tooling is missing, commands fail, YAML changes do not apply, status disagrees, or services never become ready. Do not use for routine status views or authorized routine start, stop, and restart.