「service」の検索結果

Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using Multi-Window Multi-Burn-Rate SLO alerts, memory saturation, and cluster health such as CrashLoopBackOff and Node NotReady conditions. Don't use for non-GKE compute runtimes such as standalone Compute Engine VMs or standalone Cloud Run services without GKE.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill to configure SLA enforcement for Salesforce Field Service (FSL) using Work Order entitlement processes: designing entitlement processes of type Work Order, defining FSL milestones (response time, on-site arrival, resolution), wiring milestone actions, and aligning Business Hours with service territory Operating Hours. NOT for Case SLAs and Case entitlement processes — use admin/entitlements-and-milestones. NOT for defining the SLA tier table and escalation matrix — use architect/sla-design-and-escalation-matrix.

日本語の概要は準備中です。原文の説明を表示しています。

Configure and manage Field Service Lightning work orders: work types, work order line items, service appointments, status flow, and auto-creation via maintenance plans. NOT for choosing which technician gets the appointment (work rules, scheduling policies) — use admin/fsl-scheduling-policies. NOT for setting up the technicians, their skills or capacity — use admin/fsl-resource-management.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill to create, configure, or tune Field Service Lightning scheduling policies — including work rules (pass/fail filters) and service objectives (weighted ranking criteria). Covers the four default policies, custom policy design, work rule type selection, and objective weighting strategy. NOT for running or tuning the Optimizer itself — use admin/fsl-scheduling-optimization-design. NOT for resource skills and preferences — use admin/fsl-resource-management. NOT for resource capacity records — use admin/fsl-capacity-planning.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when configuring, extending, or troubleshooting the Salesforce Field Service (FSL) Mobile app for field technicians — including offline priming strategy, app extensions, deep linking, and custom branding. Trigger keywords: FSL mobile, Field Service mobile app, offline priming, mobile extension toolkit, app extensions for field service. NOT for coding the LWC quick action or offline extension itself — use apex/fsl-mobile-app-extensions. NOT for technician job lifecycle, signature capture, or parts consumption — use admin/fsl-mobile-workflow-design.

日本語の概要は準備中です。原文の説明を表示しています。

Use when configuring or operating the native Salesforce Data Export Service (Setup → Data Export) — weekly or monthly CSV export, attachment inclusion, file-size split, the 48-hour download window, and the gap between this free utility and the paid Salesforce Backup and Restore product. Triggers: 'data export service', 'weekly export', 'export attachments', 'data export 48 hour download', 'data export missing objects', 'is weekly export a backup', 'bulk api 2.0 query job export', 'data loader extract batch', 'process-conf.xml export', 'incremental export systemmodstamp', 'export inventory retention owner'. NOT for the paid Salesforce Backup and Restore product (use that as a separate tool), NOT for Bulk API extraction (use data/bulk-api-patterns), NOT for HA/DR architecture (use architect/ha-dr-architecture).

日本語の概要は準備中です。原文の説明を表示しています。

Use when writing or reviewing TypeScript backend tests — Jest unit tests for services/controllers (mocked Prisma) or Supertest integration tests against a real isolated PostgreSQL test database. Triggers on edits to `*.service.test.ts`, `*.controller.test.ts`, `*.integration.test.ts`, service/controller/API test files (`.ts`, not `.tsx`) under `**/__tests__/`, or mentions of "backend test", "service test", "API test", "database test".

日本語の概要は準備中です。原文の説明を表示しています。

Drafts certificates of service (proofs of service) for court filings. Use when a filing must be accompanied by proof that copies were served on all parties or counsel. Covers FRCP Rule 5, state equivalents, ECF/e-service, U.S. mail, hand delivery, and overnight courier methods.

日本語の概要は準備中です。原文の説明を表示しています。

Design and implement backend service changes: API contracts, service boundaries, auth integration, reliability and delivery checks. Use for backend/API handlers, services, webhooks, jobs, or backend architecture changes. Routes schema/migrations to mk:database; security review to the existing security workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user says 'create service', 'new service class', or needs a PHP service following SOLID principles with proper DI and repository usage.

日本語の概要は準備中です。原文の説明を表示しています。

Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.

日本語の概要は準備中です。原文の説明を表示しています。

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".

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Consul Connect — hashiCorp Consul Connect service mesh management covering service discovery, intentions, sidecar proxies, mesh gateways, ingress/terminating gateways, certificate management, and health checks. Use when managing Consul Connect mesh, configuring service-to-service authorization, debugging proxy connections, or managing mesh gateways for multi-datacenter communication.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Chamber — chamber secrets management using AWS Systems Manager Parameter Store, service-scoped secret organization, environment variable export, and parameter auditing. Covers reading and writing secrets by service, comparing environments, listing services, version tracking, and IAM permission validation. Use when managing AWS SSM-based secrets with Chamber, auditing parameter changes, or comparing configs across services.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Aws Proton — aWS Proton service and environment template management. Covers environment templates, service templates, service instances, pipeline management, component inspection, and template sync configuration. Use when managing Proton environments, deploying services from templates, inspecting provisioned resources, or auditing template versions.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Aws Service Catalog — aWS Service Catalog portfolio and product management. Covers portfolio administration, product versioning, provisioned product inspection, launch constraints, tag options, and sharing across accounts. Use when managing self-service IT catalogs, provisioning products, reviewing portfolios, or auditing product usage across an organization.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Aws App Runner — aWS App Runner service management and health analysis. Covers service inventory, deployment status, auto-scaling configurations, custom domain associations, VPC connector settings, and observability configurations. Use when inspecting App Runner services, debugging deployment failures, reviewing scaling behavior, or auditing service configurations.

日本語の概要は準備中です。原文の説明を表示しています。

Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.

日本語の概要は準備中です。原文の説明を表示しています。

Android Accessibility Service security analysis and pentesting. Use this skill whenever the user mentions Android security testing, accessibility service abuse, RAT detection, malware analysis, ClayRat, PlayPraetor, overlay phishing, credential harvesting, or any Android app security assessment involving AccessibilityService APIs. This skill helps detect malicious accessibility services, analyze abuse patterns, and harden apps against accessibility-based attacks.

日本語の概要は準備中です。原文の説明を表示しています。

Google Workspace CLI (gws) リファレンス。Rust 製。 `gws <service> <resource> <method>` 形式で Gmail / Drive / Calendar / Sheets / Docs / Chat 等 19 サービスを統一操作。Google Discovery Service 経由の動的コマンド生成。 `+` プレフィックスのヘルパーコマンド（+send, +agenda, +upload, +triage 等）、 ワークフロー合成（+standup-report, +meeting-prep, +weekly-digest）、 OAuth / サービスアカウント / CI ヘッドレス認証、env vars / .env / keyring 設定、 グローバルフラグ（--dry-run, --page-all, --sanitize）、exit codes、Model Armor 統合。

Wear OS (Kotlin) の androidx.wear API・Watch Face Format (WFF) リファレンス。 Wear Compose の CurvedLayout, rotary input, ambient mode, ScalingLazyColumn。 Tiles / ProtoLayout, ComplicationDataSourceService と ComplicationData 型, Health Services (MeasureClient, ExerciseClient, PassiveMonitoringClient), WFF の XML 要素・式・コンプリケーションスロット・ユーザー設定。

Android アプリ開発 (Kotlin) の Media3 / CameraX リファレンス。androidx.media3, androidx.camera。 ExoPlayer, MediaSession, MediaSessionService, MediaLibraryService, DRM, Compose UI (PlayerSurface), ProcessCameraProvider, CameraSelector, ImageCapture, ImageAnalysis, VideoCapture, CameraInfo, CameraX Extensions, Camera2 Interop。

Find and identify the CCSPlayer_ItemServices_DropActivePlayerWeapon virtual function in CS2 binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the "drop the currently held weapon" vfunc by RTTI-walking the CCSPlayer_ItemServices vtable and confirming the candidate reads the player's active weapon and forwards it, with a computed toss velocity, into the weapon's own drop vfunc. Trigger: CCSPlayer_ItemServices_DropActivePlayerWeapon

日本語の概要は準備中です。原文の説明を表示しています。

Refactors route handlers into service layer with clean boundaries, dependency injection, testability, and separation of concerns. Provides service interfaces, folder structure, testing strategy, and migration plan. Use when refactoring "fat controllers", "business logic", "service layer", or "architecture cleanup".

日本語の概要は準備中です。原文の説明を表示しています。