Results for “gate”

Defines cell populations in flow and spectral cytometry through manual gates (rectangle, polygon, quadrant, boolean) and reproducible automated gating (openCyto gating templates, flowDensity data-driven thresholds, flowClust model-based gates), organized as a hierarchical GatingSet (flowWorkspace) and round-tripped with FlowJo via CytoML. Covers the canonical gate order (time -> debris -> singlets -> live -> lineage), FMO-vs-isotype boundary setting, gate-order dependence and recompute semantics, rare-event/MRD gating, and per-population statistics. Use when building a gating strategy, automating a manual FlowJo scheme across samples, choosing manual vs data-driven gates, or extracting population frequencies.

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

This skill should be used when the user asks to "dev-navigate", "どこから始めれば", "何を使えばいい", "スキルを選んで", "ナビ", "navigate", "which skill", "how to start", "開発の進め方", "何から始める". 開発者がやりたいことをヒアリングし、最適なtsumikiスキルとその実行順序をナビゲーションする。

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

Expert knowledge for Azure VPN Gateway development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring S2S/P2S tunnels, BGP/NAT, IPsec/IKE crypto, VPN client auth, or cross-cloud/ExpressRoute VPNs, and other Azure VPN Gateway related development tasks. Not for Azure Virtual Network (use azure-virtual-network), Azure Virtual WAN (use azure-virtual-wan), Azure ExpressRoute (use azure-expressroute), Azure Application Gateway (use azure-application-gateway).

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

Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness. Produces a concise review pack, records risks and verification, and blocks landing until a human explicitly approves or approves with required fixes.

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

Strategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is a generic example, not the SSOT. Plans and gates only: never dispatches, never closes open-items. The plan-gate (one seat, a second on BLOCK) runs only on an explicit plan-gate step. (Renamed from `pm` 2026-07-05 — `/pm`/`@pm` still resolve via the backward-compat alias in `.claude/skills/pm/SKILL.md`.)

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

Strategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is a generic example, not the SSOT. Plans and gates only: never dispatches, never closes open-items. The plan-gate runs one seat, a second on BLOCK, and runs only on an explicit plan-gate step. (Renamed from `pm` 2026-07-05 — `/pm`/`@pm` still resolve via the backward-compat alias in `.claude/skills/pm/SKILL.md`.)

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

Defines cell populations in flow and spectral cytometry through manual gates (rectangle, polygon, quadrant, boolean) and reproducible automated gating (openCyto gating templates, flowDensity data-driven thresholds, flowClust model-based gates), organized as a hierarchical GatingSet (flowWorkspace) and round-tripped with FlowJo via CytoML. Covers the canonical gate order (time -> debris -> singlets -> live -> lineage), FMO-vs-isotype boundary setting, gate-order dependence and recompute semantics, rare-event/MRD gating, and per-population statistics. Use when building a gating strategy, automating a manual FlowJo scheme across samples, choosing manual vs data-driven gates, or extracting population frequencies.

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

**MANDATORY before every commit and push.** All gates must pass — Gates 1–3 always run; Gates 4 (Docker) and 5 (Cloud) run only when applicable. Do NOT proceed if any gate fails — fix the issue first.

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

Configures the JetFormBuilder action events system — the named events (DEFAULT.PROCESS, DEFAULT.REQUIRED, GATEWAY.SUCCESS, GATEWAY.FAILED, BAD.REQUEST, ON.DYNAMIC_STATE, never) that decide WHEN a Form Action runs. Covers declaring supported / unsupported / required events on a custom action, the validation precedence inside Base_Event::is_valid_action(), the multi-event subscription model the action editor exposes, and how to register a brand-new event type via the 'jet-form-builder/event-types' filter using Base_Event, Base_Action_Event, or Base_Gateway_Event. Use when an action needs to run only on payment callbacks, only on validation failure, only on a specific conditional state, after another action's hidden flow, or when the plugin needs to define its own event class (e.g. for inbound webhooks). Triggers on mentions of "JFB events", "action events", "GATEWAY.SUCCESS", "DEFAULT.PROCESS", "supported_events", "unsupported_events", "get_required_events", "Base_Event", "Base_Gatewa...

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

OpenClaw API gateway proxy for authenticated SaaS calls (100+ services in references/SERVICES.md). Use ONLY when making an HTTP request to a third-party service that requires the gateway's stored credentials. NOT for direct API calls with bearer tokens already in scope, NOT for monday.com (use monday-for-agents), NOT for WhatsApp (use heleni-whatsapp). Triggers: "call the X API", "fetch from <service>", "send to Slack via gateway", "use the gateway for".

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

Use when working with Aws Fargate — aWS Fargate task and service analysis covering ECS cluster inventory, Fargate task status, CPU and memory utilization, task definition review, networking configuration, service auto-scaling policies, and container health checks. Use for Fargate-specific workload optimization.

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

Defines cell populations in flow and spectral cytometry through manual gates (rectangle, polygon, quadrant, boolean) and reproducible automated gating (openCyto gating templates, flowDensity data-driven thresholds, flowClust model-based gates), organized as a hierarchical GatingSet (flowWorkspace) and round-tripped with FlowJo via CytoML. Covers the canonical gate order (time -> debris -> singlets -> live -> lineage), FMO-vs-isotype boundary setting, gate-order dependence and recompute semantics, rare-event/MRD gating, and per-population statistics. Use when building a gating strategy, automating a manual FlowJo scheme across samples, choosing manual vs data-driven gates, or extracting population frequencies.

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

Defines cell populations in flow and spectral cytometry through manual gates (rectangle, polygon, quadrant, boolean) and reproducible automated gating (openCyto gating templates, flowDensity data-driven thresholds, flowClust model-based gates), organized as a hierarchical GatingSet (flowWorkspace) and round-tripped with FlowJo via CytoML. Covers the canonical gate order (time -> debris -> singlets -> live -> lineage), FMO-vs-isotype boundary setting, gate-order dependence and recompute semantics, rare-event/MRD gating, and per-population statistics. Use when building a gating strategy, automating a manual FlowJo scheme across samples, choosing manual vs data-driven gates, or extracting population frequencies.

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

Verify OpenClaw installation, onboarding, gateway operation, and upgrades in Parallels virtual machines running macOS, Windows, or Linux. The skill guides baseline restoration, bounded test runs, log interpretation, and focused retries when checks fail.

• Checking fresh OpenClaw installs across three operating systems
• Verifying upgrades through the installed OpenClaw updater
• Restoring existing VM snapshots for repeatable checks

Investigate Node.js bugs by pausing execution, examining variables, and stepping through code. Diagnose stalled asynchronous work and unreliable tests, or collect memory snapshots and CPU profiles to investigate growing memory use and slow execution.

• Investigate stalled asynchronous work
• Debug tests that fail inconsistently
• Examine startup timing and child processes

Investigate a question using official documentation, source code, specifications, and first-party APIs. A background agent records the findings in one Markdown file with sources for each claim, following the repository’s existing conventions for research notes.

• Verify API behavior against official sources
• Save research findings with citations
• Delegate reading while continuing other work

Coordinate feature work, bug fixes, refactoring, and MVP development through shared phases scaled to the change. Related operation skills use this workflow to delegate research, planning, test-first implementation, review, and commits with human approval checkpoints.

• Using a shared process for feature additions and bug fixes
• Scaling development steps to the size of a change
• Organizing MVP development from a design document

Connect a remote Hermes gateway to MCP servers that require OAuth, a browser-based authorization process. The skill covers dashboard access, manual token setup when needed, and diagnosis of expired tokens or revoked sessions.

• Connect a remote Hermes gateway to an OAuth MCP server
• Resolve localhost callback failures during authorization
• Set up manual authorization without an interactive terminal

Delegate work to an existing Paperclip agent by selecting a suitable assignee and creating a task with clear objectives, constraints, and deliverables. Receive a lasting task reference and check progress after the conversation ends.

• Assign requested work to an existing agent
• Create tasks with clear constraints and deliverables
• Keep a task link for follow-up after the conversation

Review AI call logs by provider, model, time range, status, and cost. Aggregate token usage, export logs, configure budgets, and inspect response times and prompt cache statistics to understand usage and performance.

• Investigate failed calls in filtered logs
• Aggregate token usage and costs across connections
• Configure budgets and token limits

Check and add structured data that describes user reviews and average ratings on product or service pages. Verify required fields against real reviews and validate the markup for star-rating search results.

• Audit review markup on product pages
• Add average ratings from genuine user reviews
• Validate eligibility for star-rating search results

Delegate repository analysis or coding tasks to Qwen Code without opening its interactive interface. Run within a specified project and time limit, then check the JSON response and exit status before summarizing the result.

• Investigate a failing test without editing files
• Delegate repository analysis to Qwen Code
• Request coding changes within an explicitly approved scope

Delegate a bounded local task to Hermes Agent in a single run and receive its text result. The workflow accounts for automatic tool approval, isolates read-only work, and inspects file changes after authorized edits.

• Delegate local analysis using a read-only or disposable copy
• Ask Hermes Agent to edit explicitly named files
• Review exit status and file changes after delegated work

Build and deploy AWS Lambda functions without managing servers. Guidance covers APIs, scheduled jobs, event triggers, permissions, shared dependencies, and performance tuning, with code and command examples for deployment and troubleshooting.

• Building lightweight APIs with API Gateway or function URLs
• Running scheduled jobs with EventBridge
• Processing S3 uploads or SQS messages