القائمة
AWS and Terraform via loctl. Use when checking AWS resources, S3 buckets, EKS clusters, or running terraform plans.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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-aws |
| description | AWS and Terraform via loctl. Use when checking AWS resources, S3 buckets, EKS clusters, or running terraform plans. |
The qa/ops prefix has no effect on aws/terraform -- both prefixes use the same credentials and targets (the prefix only routes observability/ArgoCD endpoints).
AWS_PROFILE is set to the role in ~/.loctl/config.yaml (default vungle2-EngineeringRole; check/switch with loctl role) -- server-side safety is exactly that role's IAM policyapply, destroy, import, etc. are blocked client-side--help flag anywhere in the args bypasses the terraform gatingloctl qa aws sts get-caller-identity
loctl ops aws s3 ls
loctl ops aws eks describe-cluster --name <cluster-name> --region us-east-1
Allowed subcommands: init, plan, show, output, providers, version, fmt, validate, graph, state list, state show, state pull. Everything else is blocked.
loctl runs the terraform binary directly (it never invokes tfswitch); the binary must already be installed -- loctl setup uses tfswitch to install it.
loctl qa terraform init
loctl qa terraform plan
loctl ops terraform show
loctl ops terraform state list
loctl ops terraform validate