dstack-run

Plugin dstack-run from marketplace dstack in gosuda/dalcom-skills. Commands read from the repo's manifest — 3 days ago.

Skills (20)

• append-run-log

  Use when a completed agent run must be recorded as durable, queryable evidence. Not for remote, credential, publish, deploy, or irreversible changes.

• artifact-arena

  Use when asked to run /artifact-arena to generate and judge competing artifact implementations. Not for remote, credential, publish, deploy, or irreversible changes.

• cybernetic-loop

  Use when the caller supplies a falsifiable out-of-happy-path invariant and a finite budget. Restores via bounded patches or reverts. Not for normal feature delivery or universal retries.

• diagnose-loop-health

  Use when a configured loop misbehaves, produces unexpected results, or its setup soundness is questioned. Not for tasks that require source or remote-system changes, not for loop design.

• diamond-task

  Use when one issue or PR is too large for a worker and partitions into disjoint write sets. Not for independent parallel tasks: use parallel-launch. No remote or irreversible changes.

• feedback-sweep

  Use when asked to /feedback-sweep [setup|reconfigure] [mode:non-interactive]. Not for discovering recurring feedback patterns.

• figure-it-out

  Use when non-trivial work should run a matched playbook to verified real-surface completion, or a bespoke workflow when none fits. Not for remote, credential, publish, deploy, or irreversible changes.

• goal-prompt-drafting

  Use when asked to draft copy-ready /goal objectives for long-running agents. Not for source or remote-system changes.

• guardrail-carve-run

  Use when guardrail-adjacent material (stealth, scraping, privacy, IP, policy, security) or mixed reversible/irreversible, sensitive work, or the user says "autobahn this". Not for carved risky work.

• implement-spec

  Use when a ticket DAG from a complete specification needs parallel execution into a verified integration branch, with an optional green draft pull request or merge request on explicit approval. Not for a settled ticket with no spec and not for ticket decomposition.

• orchestration-patterns

  Use when work decomposes across subagents or role panels and needs coupling-based orchestration. Not for cloud-agent task-graph orchestration.

• partition-scopes-to-subagents

  Use when asked to partition non-overlapping scopes across subagents and drive each to completion. Not for concurrent independent sub-tasks: use parallel-launch.

• schedule-dependency-waves

  Use when work units carrying declared dependencies must be ordered into execution waves before any dispatch, including detecting a dependency cycle. Not for partitioning one issue into disjoint write sets: use diamond-task. Not for concerns with no dependencies: use parallel-launch.

• scheduler

  Use when asked to set, list, pause, update, or delete a reminder or local task that fires at a confirmed time or interval. Not for destructive, remote, credential, publish, or deploy operations.

• show-me-your-work

  Use when the user invokes it to append a structured decision record to an append-only TSV log, ending with an Attention section for reviewers. Not for an ephemeral visual: use show-me.

• size-the-run

  Use when a run could be over- or under-powered, before dispatching a subagent, or the user asks how hard to think about a task. Recommends one tier and effort level. Not for executing the sized task.

• watch-for-harness-mode

  Use when a proven watch pattern should become a reusable harness artifact with configurable inputs. Not for remote, credential, publish, deploy, or irreversible changes.

• watch-for-structured

  Use when the user wants to classify a surface state and page an on-call API when triggered. Not for read-only anomaly watching without paging: use watch-for.

• watch-for

  Use when monitoring a file, log, endpoint, or artifact for drift or errors, or polling a target until a predicate holds. Modes: watch (default), until. Not for source or remote-system changes.

• wizard

  Use when a human must perform steps only they can, such as provisioning infrastructure, entering credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Not for steps the agent can perform itself.

Similar plugins