Results for “service”

The branded entry point to ServiceGraph — use whenever the user explicitly names **ServiceGraph** — "use ServiceGraph to…", "what datasets does ServiceGraph have", "search ServiceGraph for…", "look this up in ServiceGraph", "pull contacts from ServiceGraph for these domains", "how many credits do I have on ServiceGraph". ServiceGraph is a multi-dataset platform of metrics-enriched business data for founders — where to launch, who to email, who to hire. This skill explains how to drive the API (api.servicegraph.co / mcp.servicegraph.co) against ANY dataset — discover what datasets exist, discover a dataset's schema and filters, search free brief rows, and unlock contact + metric detail with credits. Dataset-agnostic by design — it discovers everything through the API and never assumes which datasets or fields exist. When the user describes an intent WITHOUT naming ServiceGraph (e.g. "find a PR agency in NY"), defer to the matching specific skill (find-pr-agency, find-marketing-agency, find-law-firm, …); this skill is for explicit ServiceGraph requests and for datasets no specific skill covers yet. Skip non-US firms, consumer/personal services, and individual freelancers.

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

Manage the KubeSphere ServiceMesh extension built on Istio, Kiali, and Jaeger. Install or remove it, check deployment status, and investigate problems with staged releases, proxy injection, service topology, traffic metrics, and tracing across application components.

• Installing, upgrading, or removing ServiceMesh
• Investigating staged release routing problems
• Checking missing Istio proxy containers

Manage embedded services such as 9Router and CLIProxyAPI through local service APIs. Install, start, stop, restart, or update services, then check their status, retrieve logs, and configure automatic startup.

• Installing and starting embedded services
• Stopping or restarting services
• Checking service status and logs

Plan microservices by defining service responsibilities, communication methods, and data ownership. Use patterns for gradual migration, distributed transactions, and failure isolation to design systems made of independently responsible services.

• Gradually splitting a monolithic system into services
• Defining service responsibilities and interfaces
• Designing event-based communication and distributed transactions

Diagnose why GKE Pods cannot authenticate to Google Cloud APIs. Inspect cluster settings, service account bindings, resource permissions, and metadata server health, then provide evidence and concrete fixes for a human to apply.

• Investigate Pod authentication failures and 403 errors
• Check Kubernetes service account identity bindings
• Diagnose metadata server connectivity problems

Design systems made of independently deployable services, or plan how to split an existing application. The skill produces service boundary diagrams and recommendations for communication, data ownership, failure handling, monitoring, and deployment.

• Planning how to split a monolithic application
• Choosing REST, gRPC, or event-based communication
• Defining data ownership and cross-service consistency

Expert knowledge for Azure Service Fabric development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when designing Service Fabric clusters, Reliable Services/Actors, reverse proxy/API gateways, CRP/CRM settings, or sfctl automation, and other Azure Service Fabric related development tasks. Not for Azure Kubernetes Service (AKS) (use azure-kubernetes-service), Azure Container Apps (use azure-container-apps), Azure App Service (use azure-app-service), Azure Virtual Machines (use azure-virtual-machines).

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

Use whenever the user wants to find, shortlist, vet, enrich, or research US professional-services firms — law, marketing, consulting, accounting, IT services, architecture, engineering, HR, PR, design, and similar B2B service providers. Triggers on requests like "find me a PPC agency in California", "shortlist three boutique IP law firms", "build a longlist of 50 mid-size IT consultancies", or "here are 12 agency domains — pull contact info and confirm which are US-based", even when the need is described indirectly without naming a category. Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog with filters for industry, services, location, size, ratings, and third-party listings. Skip when the user is asking for personal/consumer services for themselves (an individual's own legal, tax, or medical needs), non-US firms, individual freelancers, retail/ecommerce/SaaS-product companies, recruiting-an-employee tasks, or general web research that doesn't need a structured firm directory.

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

Use this skill to configure Field Service Lightning service resources — including ServiceResource types, skill assignments via ServiceResourceSkill, capacity-based resource setup, and ResourcePreference rules. NOT for territory-level WorkCapacityLimit throttling or capacity-vs-utilization reporting — use admin/fsl-capacity-planning. NOT for service territory setup — use admin/fsl-service-territory-setup. NOT for work rules and service objectives — use admin/fsl-scheduling-policies.

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

Inbound email processing in Salesforce via Email Services + the `Messaging.InboundEmailHandler` Apex interface. Covers EmailService configuration (running user, accept-from address, attachment handling, error / failure routing), the EmailServicesAddress per-routing-address pattern, the handler's `Messaging.InboundEmail` payload (text body, HTML body, headers, attachments, in-reply-to threading), and the canonical Email-to-Case alternative for case creation. NOT for outbound email (use admin/email-templates-and-alerts), NOT for Email-to-Case flow customization itself (use admin/email-to-case-configuration). Trigger keywords: EmailServicesFunction, EmailServicesAddress, runAsUser, localPart, EmailDomainName, attachmentOption, overLimitAction, errorRoutingAddress, routing address, inbound email limit.

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

Create a custom offline page and configure a service worker, a browser background script, to cache it in advance. Show it when page navigation fails, and review resource dependencies and fallback conditions.

• Add an offline page to a PWA
• Guide users during connection loss
• Review offline page caching

Set up monitoring for communication between services in Istio or Linkerd environments. Combine metrics, logs, and distributed traces, which follow requests across services, to investigate delays and errors, visualize dependencies, and define service quality targets.

• Trace requests across multiple services
• Create communication metrics and dashboards
• Investigate latency, errors, and connectivity issues

Investigate service account misuse by examining unexpected interactive logons, privilege changes, and movement between systems. Correlate endpoint and security logs, distinguish suspicious activity from legitimate operations, and document evidence, risk, and recommended responses.

• Investigating unexpected interactive logons by service accounts
• Checking service account access outside its assigned scope
• Tracing suspicious movement between systems after hours

Start and manage long-running background services such as development servers. Check their status and output logs, verify listening ports, retrieve local URLs, and restart services while keeping the same service ID.

• Starting a development server in the background
• Checking service status and output logs
• Restarting a service while keeping its ID

Configure dependency injection in .NET MAUI, a way to supply objects with the services they need. Covers service registration, instance lifetimes, page and ViewModel constructors, Shell navigation, platform implementations, and test substitutions.

• Register services, Pages, and ViewModels
• Choose shared or freshly created service instances
• Connect Shell navigation with constructor injection

Debug 404 errors for API endpoints in microservice architectures where code exists but routing sends requests to wrong service. Use when: (1) API endpoint returns 404 despite code being deployed, (2) Multiple services share same hostname via HTTPRoute/Ingress, (3) Service logs show "Health server" but you expected API endpoints, (4) Monorepo deploys multiple images and endpoint might be in different service than expected. Covers: verifying which service handles which paths, HTTPRoute path precedence, testing endpoints directly from inside cluster, matching image tags across services.

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

Service-oriented and microservices architecture patterns for cloud-scale systems. Covers service boundaries, API versioning and backward compatibility, eventual consistency at the API layer, idempotency keys, saga and choreography patterns, bulkheads, circuit breakers, service meshes, and the Vogels "you build it, you run it" operating principle. Use when designing service decomposition, API contracts, inter-service communication, or reviewing a proposed microservices architecture for coupling and resilience.

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

Find and identify the CCSPlayer_ItemServices_GiveNamedItem virtual function, the CCSPlayer_WeaponServices_Weapon_GetSlot helper, and the CBasePlayerPawn_RemovePlayerItem helper in CS2 binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate GiveNamedItem by RTTI-walking the CCSPlayer_ItemServices vtable, then to locate the other two by decompiling the already-known CCSPlayer_ItemServices_GiveDefaultItems anchor and matching its callees' argument shapes and inventory-slot bookkeeping semantics. Trigger: CCSPlayer_ItemServices_GiveNamedItem, CCSPlayer_WeaponServices_Weapon_GetSlot, CBasePlayerPawn_RemovePlayerItem

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

Find and identify the CCSPlayer_WeaponServices_EquipWeapon function and the CCSPlayer_WeaponServices_CanUse virtual function in CS2 binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the weapon-equip helper and the "is this weapon usable right now" vfunc by RTTI-walking the CCSPlayer_WeaponServices vtable and confirming each candidate's decompiled body against the known CCSPlayer_WeaponServices_PickupItem anchor's callee shapes. Trigger: CCSPlayer_WeaponServices_EquipWeapon, CCSPlayer_WeaponServices_CanUse

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

Configure how traffic moves between services in Istio, a system for managing service communication. Includes routing, load balancing, gradual releases, retries, failure isolation, copied traffic for testing, and commands for inspecting configuration.

• Send a small share of traffic to a new service version
• Configure retries, timeouts, and failure isolation
• Copy traffic to a test environment

Investigate Kerberoasting, an attack that targets service account passwords, using Active Directory authentication logs. Examine unusual service ticket requests, correlate endpoint and network evidence, and organize findings with risk levels and recommended response actions.

• Hunting for unusual service ticket requests
• Investigating suspected service account password attacks
• Validating alerts and organizing response evidence

Write, review, and upgrade Effect v4 code for Composio CLI and its related packages. It guides service definitions, typed errors, command APIs, and version alignment, checking unfamiliar APIs against source files and installed type definitions.

• Implementing and reviewing Effect v4 code
• Defining services and typed error recovery
• Checking effect/cli APIs

Plan and configure GKE cluster networks, including private nodes, IP address ranges, DNS, and outbound connectivity. Use the guidance to set up VPC-native networking and Dataplane V2, which provides built-in network policy enforcement.

• Designing a private GKE cluster network
• Planning IP ranges for Pods, Services, and nodes
• Configuring outbound access with a static source IP

Guides development of Native SDK TypeScript services for file access, network requests, and other work outside the deterministic core. Covers typed calls, pinned npm dependencies, streaming, cancellation, replay, and process or thread execution.

• Adding or updating Native SDK TypeScript services
• Moving file access or JSON processing out of the core
• Investigating NS1065–NS1067 errors