Menu
ArgoCD via loctl. Use when checking deployment status, sync health, or app history.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Coordinate full-strength Claude and Codex teammates in detached tmux sessions with external stall monitoring, durable file channels, completion markers, and resumable conversations. Use when work can be divided into independent tasks, when the user asks for teammates or subagents, or when delegating research, implementation, frontend, review, or long-running work across model accounts.
Coordinate full-strength Claude and Codex teammates in detached tmux sessions with external stall monitoring, durable file channels, completion markers, and resumable conversations. Use when work can be divided into independent tasks, when the user asks for teammates or subagents, or when delegating research, implementation, frontend, review, or long-running work across model accounts.
Drive the kautopilot binary as a thin in-session controller: ticket/free-form request → merge-ready PRs across one or more repos, as ONE flat session. The binary owns all state, prompts, and next-step decisions; this skill just runs what `kautopilot next` yields. Use when running /kautopilot.
Drive the kautopilot binary as a thin in-session controller: ticket/free-form request → merge-ready PRs across one or more repos, as ONE flat session. The binary owns all state, prompts, and next-step decisions; this skill just runs what `kautopilot next` yields. Use when running /kautopilot.
Iteratively review-and-resolve the current changes using parallel subagent reviewers across multiple lenses (bugs, quality, completion), looping until every reviewer is satisfied. Use when running /floop, or when asked to deeply review and harden a diff until all critiques are addressed.
Give the user a fast, ADHD/dyslexia-friendly recap of the current work or conversation — the outcome first, then what (if anything) you need from them. Use when running /summary, or when asked to "summarize", "recap", "where are we", "catch me up", or "what do you need from me".
| name | liftoff-argocd |
| description | ArgoCD via loctl. Use when checking deployment status, sync health, or app history. |
--server argocd.qa.vungle.io--server argocd.ops.vungle.ioThe --server flag is automatically prepended.
--server; argocd subcommands are not gated client-side. Stick to read commands: app list, app get, app history.loctl qa argocd app list
loctl ops argocd app list
loctl qa argocd app get <app-name>
loctl ops argocd app history <app-name>
Reads work anonymously -- no login is needed, and loctl auth deliberately skips argocd login because logging in grants write access.
Do not run argocd login. If read commands fail with 401/permission denied, stop and ask a human: logging in would hand the agent write-capable ArgoCD credentials.