Results for “gate”

Build, manage, and operate APIs with Amazon API Gateway (REST, HTTP, and WebSocket). Triggers on phrases like: API Gateway, REST API, HTTP API, WebSocket API, custom domain, Lambda authorizer, usage plan, throttling, CORS, VPC link, private API. Also covers troubleshooting API Gateway errors (4xx, 5xx, timeout, CORS failures) and IaC templates containing API Gateway resources. For general REST API design unrelated to AWS, do not trigger.

The English summary is being prepared. Showing the original description.

Returns the frozen gate constants — question, header, option labels and descriptions, digest field-list, and preview content — for every catalog gate. Invoked by the team lead fresh on arrival at each gate and on pulse re-emissions, in the same turn as the render. The transport contract, three renders, partition rule, and authoring rubric live in swarm:workflow-rules.

The English summary is being prepared. Showing the original description.

Classify gate call variants in a minified JavaScript bundle. Covers context-window extraction around a flag occurrence, identification of 4–6 reader variants (sync boolean, sync config-object, bootstrap-aware TTL, truthy-only, async bootstrap, async bridge), default-value extraction (boolean / null / numeric / config-object literal), conjunction detection across `&&` predicates, kill-switch inversion detection, and production of a gate-mechanics record that feeds probe- feature-flag-state. Use when a flag's behavior cannot be inferred from its name alone, when the binary uses multiple reader libraries, or when config-object gates carry structured schemas distinct from boolean gates.

The English summary is being prepared. Showing the original description.

Produce the rendered evidence a human-gated frontend PR owes its reviewer: capture each changed surface (plus the before state for anything modified, plus mobile width), then generate one self-contained local HTML page the founder can open and review without checking anything out. Use when a PR is gated by the "Frontend changes are HUMAN-GATED" section of CLAUDE.md, or when the user says "/design-gate", "screenshot evidence for this PR", "prep this for founder review", "build the design evidence page", "what does this look like before and after". The page comes from a template script, not hand-written markup. Output is session-local and never committed. Do NOT use for non-gated changes: typo/grammar/factual fixes in an unchanged block, dead link targets, alt/ARIA fixes with no visual change, cache-bust bumps, or refactors with no rendered diff.

The English summary is being prepared. Showing the original description.

Designs human-in-the-loop review points for DAG workflows. Determines what to present to the human, how to collect feedback, and how to route approve/reject/modify decisions back into the DAG. Use when adding approval gates, designing review UX, or handling human feedback in agent workflows. Activate on "human review", "approval gate", "human-in-the-loop", "human gate", "approval workflow", "user review step". NOT for executing human gates at runtime (use dag-runtime with Temporal signals), general UX design, or chatbot conversation design.

The English summary is being prepared. Showing the original description.

Busabase-backed App-in-Skill dashboard for a shared LLM gateway's cost and model governance — daily spend trend, cost breakdown by service/model, a canary-rollout status board, and a deterministic cost/error anomaly list. Use when the user invokes $kelly-llm-gateway or /kelly-llm-gateway, or wants to review LLM gateway spend, model routing, canary rollouts, rollback readiness, or cost/error anomalies for services routed through one shared gateway to multiple LLM providers/models. Human actions (promote/rollback/hold a rollout, acknowledge an anomaly) write directly onto the route's own Busabase record — this skill never changes a real routing config.

The English summary is being prepared. Showing the original description.

Organize sessions and layouts in the OpenClaw Control UI, build session dashboards, and investigate display or connection problems. It covers connected clients and Gateways accessed directly or through Tailscale, with checks of both saved state and rendered screens.

• Group and pin sessions for easier navigation
• Build a dashboard within a dedicated session
• Arrange dashboard tabs and widgets

Create monitoring dashboards for Grafana, SigNoz, and similar platforms. Choose metrics around operational questions, organize panels by purpose, and define clear titles, units, filters, and thresholds to help operators assess health and bottlenecks.

• Build a Kafka monitoring dashboard
• Monitor Elasticsearch health and performance
• Track API gateway latency and errors

Build draft structures and aggregate tables for clinical case, trial, diagnostic, and safety reports from verified synthetic, de-identified, or aggregate data. Local checks flag structural and consistency issues; qualified professional review remains required.

• Prepare a structured case-report draft
• Check trial-report sections for missing items
• Format aggregate adverse-event tables

Operate the visible browser pane in a Cherry Studio conversation to navigate pages, click controls, fill forms, capture screenshots, and investigate browser issues. It can work with authenticated websites while checking page state and action outcomes.

• Navigate and operate an authenticated website
• Fill forms and verify the resulting page state
• Capture screenshots of a page or specific section

Delegate a clearly scoped coding task to Google Antigravity CLI when explicitly requested. Provides a workflow for preparing instructions, reading the implementer’s report, reviewing changes, rerunning project checks, and committing verified work.

• Delegate a clearly scoped coding task to Google Antigravity CLI
• Prepare an implementation brief with constraints and checks
• Review delegated changes and rerun project checks

Design CI/CD pipelines that move applications through development, staging, and production. Define approval and security checks, gradual release strategies, health checks, and rollback procedures, and investigate gates or deployments that fail to progress.

• Designing CI/CD pipelines across multiple environments
• Introducing canary or blue-green releases
• Investigating stalled approvals and release gates

Access external APIs for email, calendars, GitHub, and payments through OneCLI Gateway. The proxy adds stored credentials to outgoing HTTPS requests, letting agents use connected services without handling secret values directly.

• Read email through the Gmail API
• Check Google Calendar events
• View GitHub repositories or create issues

Create or update Kubernetes YAML configuration files for GKE Autopilot and Standard. Translates application requirements into manifests covering container permissions, CPU and memory allocation, health checks, storage, external routing, and GPU resources for AI model serving.

• Creating GKE application deployment manifests
• Reviewing container security and resource settings
• Configuring external routes with GKE Gateway API

Roll back Kortix production to a previously released version using existing builds. Covers frontend and backend rollback, database compatibility checks, prevention of unintended frontend rebuilds, and returning to the latest version through a later release.

• Restore a previous release after a production incident
• Check database compatibility before a rollback
• Prevent frontend rebuilds from overwriting a rollback

Delegate coding, analysis, refactoring, or reviews from Claude Code to Codex CLI. The skill explains unattended execution, permission settings, output capture, parallel tasks, and independent checks of changed files and test results.

• Delegate implementation while retaining planning responsibility
• Get a second opinion on code changes
• Split independent tasks across separate git worktrees

Assess externally exposed enterprise SSL VPN gateways by identifying products, checking known vulnerabilities, and reviewing authentication backends and SAML settings. The skill provides vendor-specific checks and a staged workflow that starts with less disruptive identification before deeper testing.

• Identify products behind exposed SSL VPN portals
• Triage known vulnerabilities by VPN vendor
• Review SAML settings on remote-access gateways

Delegate a coding task to the Cline coding agent CLI (`cline`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Cline - phrasings like "have Cline implement X", "delegate this to cline", "run it through Cline", or "use cline to implement/fix/refactor" - or wants to run a queue of coding tasks through Cline while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

The English summary is being prepared. Showing the original description.

Delegate a coding task to the Pi coding agent CLI (`pi`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Pi - phrasings like "have Pi implement X", "delegate this to pi", "run it through Pi", or "use pi to implement/fix/refactor" - or wants to run a queue of coding tasks through Pi while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

The English summary is being prepared. Showing the original description.

Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself. Use only when the user explicitly asks to delegate implementation to Claude Code, another Claude session, or the `claude` CLI — for example, "have another Claude implement this", "delegate this to Claude Code", or "run this queue through a separate Claude session." Do not trigger merely because the current orchestrator is Claude, and do not use when the user asks the current Claude to implement directly without delegation.

The English summary is being prepared. Showing the original description.

Delegate a coding task to the GitHub Copilot CLI (`copilot`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Copilot - phrasings like "have Copilot implement X", "delegate this to copilot", "run it through Copilot CLI", or "use copilot to implement/fix/refactor" - or wants to run a queue of coding tasks through Copilot while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

The English summary is being prepared. Showing the original description.

Run inference on Fireworks AI — direct, through the Leanmcp AI Gateway proxy (aigateway.leanmcp.com) for observability, or via LiteLLM / the OpenAI SDK / raw HTTP. Covers the endpoint-and-key matrix for each route, serverless vs dedicated deployments and their cold starts, browsing and filtering the model catalogue, reasoning models that return content:null with the answer in reasoning_content, function calling, concurrency and load testing, and runner scripts where many models share one protocol with a --use-proxy toggle. Use this skill whenever the user mentions Fireworks, FIREWORKS_API_KEY, api.fireworks.ai, fireworks_ai/ model ids, accounts/fireworks/models/..., a Fireworks deployment id, the Leanmcp gateway or LEANMCP_API_KEY, app.leanmcp.com observability, or gpt-oss / kimi / glm / qwen / deepseek served on Fireworks; wants to route LLM calls through a proxy for logging or cost tracking; is debugging empty responses, 404s, scope errors, cold starts, or "the gateway isn't working"; wants to pick a Fireworks model with tool calling; or wants to sweep several models over one benchmark. Reach for it even on vague asks like "why is this model returning nothing" or "set up inference for these models" when Fireworks is in play.

The English summary is being prepared. Showing the original description.

Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding. Use when the user asks about quality gates, milestone checks, phase transitions, approval steps, go/no-go decision points, or preventing cascading errors across a multi-step workflow. Produces acceptance criteria checklists, automated CI gate configurations, manual sign-off requirements, and conditional review rules for scenarios such as security changes, API changes, or database migrations.

The English summary is being prepared. Showing the original description.

Reapply and repair Windows Codex Desktop after Store upgrades, including custom provider models hidden by Statsig available_models filtering, the dependent blue-purple Power slider and its Ultra toggle, Fast Mode request/UI gates, locale i18n, plugin UI gates, Chrome/browser_use gates, Goal command gates, Windows Computer Use availability gates and plugin/runtime repair, phone remote-control pairing under third-party/API-key main app usage, Desktop dynamicTools/inputSchema thread-start schema drift, local conversation visibility recovery after model_provider switches, restored-conversation missing-cwd continuation repair, ASAR integrity repair, signing/installing patched MSIX packages, SDK cleanup, Fast Mode wire verification, local plugin marketplace registration, and optional custom model_instructions_file setup (the bundled system prompt, also called 听话水).

The English summary is being prepared. Showing the original description.