'capacity' 검색 결과

Provides data-retrieval best practices, tool selection guidance, and performant SQL query syntax for BigQuery telemetry across INFORMATION_SCHEMA, Cloud Monitoring, and the REST API. Use when the telemetry to fetch is already known, selecting telemetry tools, writing performant INFORMATION_SCHEMA queries, retrieving telemetry for diagnosing single-job performance bottlenecks, investigating slot contention, job concurrency and queue latency, analyzing reservation capacity, utilization and autoscaling saturation, or auditing capacity-based and on-demand compute and storage resource billable usage. Don't use for root-cause diagnosis or symptom troubleshooting when the cause is unknown (use bigquery-troubleshooting first), or for writing or optimizing business logic SQL (use bigquery-optimization).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configuring Salesforce Omni-Channel routing from scratch or updating existing routing: enabling Omni-Channel, creating Service Channels, configuring Routing Configurations (queue-based and skills-based), setting up Presence Statuses and Presence Configurations, assigning skills to Service Resources, and defining Skills-Based Routing Rules. Trigger keywords: Omni-Channel setup, routing configuration, queue-based routing, skills-based routing, presence status, service channel, routing rules. NOT for agent capacity units and channel weighting — use architect/omni-channel-capacity-model. NOT for Apex routing via PendingServiceRouting — use apex/omni-channel-custom-routing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan team and infrastructure capacity before it becomes a crisis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Context optimization extends the effective capacity of limited context windows through strategic compression, masking, caching, and partitioning. The goal is not to magically increase context windows but to make better use of available capacity.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews a proposal, business case, deck or plan in character as a Chief Technology Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to the exact passage, technology risks (architecture, build versus buy, vendor lock-in, security of design, engineering capacity), what would change the verdict and five interrogation questions. Use when the user asks to "run a CTO review", "pressure-test the technical side of this plan", "what would a CTO ask about this" or "rehearse the technology seat before the review". Do not use for cash, payback or budget questions, use cfo-reviewer instead; for capacity and timeline questions, use coo-reviewer; for security controls, privacy or compliance, use ciso-reviewer. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Ensure architecture/design docs state traffic assumptions, performance budgets, resource limits, and cost risks for critical paths.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with Aws Dynamodb Deep — aWS DynamoDB deep-dive management covering table configurations, capacity analysis, GSI/LSI health, auto-scaling policies, streams, backups, contributor insights, and TTL settings. Use when performing deep analysis of DynamoDB tables, optimizing capacity and throughput, debugging throttling, or auditing table configurations beyond basic inventory.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deploys infrastructure on Oracle Cloud Infrastructure (OCI) with ARM64 instances (Always Free tier eligible). Handles compartments, VCNs, subnets, security lists, and compute instances. Use when: setting up Oracle Cloud infrastructure, deploying ARM64 instances, troubleshooting OUT_OF_HOST_CAPACITY errors, optimizing for Always Free tier. Keywords: oracle cloud, OCI, ARM64, VM.Standard.A1.Flex, Always Free tier, OUT_OF_HOST_CAPACITY, oci compartment, oci vcn

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Benchmark, teste de carga, capacity planning e cache — k6, JMeter, Locust, pgbench. Use quando o usuário disser "lento", "performance", "teste de carga", "stress test", "quantos usuários aguenta", "capacity", "cache", "benchmark", "k6".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Google SRE (Site Reliability Engineering) practices distilled from the SRE book series and real Google Brain/Meta/ByteDance production experience. Covers SLI/SLO/Error Budget design, incident response, capacity planning, toil automation, monitoring golden signals, and chaos engineering principles. USE WHEN: designing reliability targets, setting up monitoring/alerting, planning capacity, reducing operational load, building incident response runbooks, implementing chaos engineering, defining error budgets, or establishing reliability culture that balances velocity with stability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deadline management and capacity planning across epics and PRs. Use when the user runs /triage or wants deadline/capacity triage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Estimates infrastructure needs based on traffic forecasts, workload analysis, and performance requirements with sizing recommendations and cost trade-offs. Use for "capacity planning", "infrastructure sizing", "resource estimation", or "scalability planning".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Claude Code가 읽는 에이전트, 스킬, 규칙, MCP 설정의 정보량을 점검합니다. 길거나 중복된 정의를 찾고 예상 절감량에 따라 개선안의 우선순위를 제시합니다.

• 컨텍스트가 빨리 차는 원인을 조사합니다
• 스킬이나 MCP 추가 후 설정을 점검합니다
• 긴 파일과 중복 지시를 확인합니다

운송사 선정, 운임 협상, 입찰, 실적 평가와 화물 배분을 지원합니다. 미국 운송 실무를 바탕으로 비용, 배송 품질, 운송 능력을 고려한 계약과 갱신 판단을 정리합니다.

• 신규 운송사 심사
• 운송 업무 입찰 준비
• 운임과 유류 할증료 협상

목표 근육과 보유 기구에 맞는 운동을 찾고 식품 영양 성분을 확인합니다. 열량 소비·체지방률·최대 중량을 추정하고 감량·증량을 위한 영양소 배분에 활용합니다.

• 보유 기구에 맞는 운동 찾기
• 식품 열량과 단백질 확인
• 감량·증량을 위한 영양소 배분

캘린더·작업·메모를 함께 살펴 한 주의 약속과 정체된 프로젝트를 돌아봅니다. 마감과 일정 부담을 고려해 다음 주 성과 목표와 다음 행동을 정리합니다.

• 완료한 약속과 기한이 지난 작업 검토
• 다음 행동이 없는 정체된 프로젝트 파악
• 답변 대기 항목과 후속 확인 일정 정리

지정한 국가의 위기 대비와 회복력을 0~100점의 종합 점수로 확인합니다. 여섯 분야의 세부 점수, 최근 30일간의 변화와 신뢰 구간도 조회합니다.

• 한 국가의 종합적인 회복력 확인
• 여섯 분야의 강점과 약점 파악
• 최근 30일간 점수 변화 조회

Coordinate tasks across multiple AI agents by tracking workloads and capacity. Redistribute queued work to available agents, adjust priorities and deadlines, and monitor resource use to identify uneven loads and scheduling bottlenecks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Redistributing tasks from busy agents to available agents
• Scheduling queued tasks by priority and deadline
• Investigating queue delays and uneven workloads

Coordinate multiple AI agents by adjusting their communication structure and task assignments as workloads change. The skill describes performance monitoring, switching coordination patterns, forecasting agent capacity, and validating changes with rollback when performance worsens.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing a coordination structure for multiple agents
• Redistributing tasks when agent workloads become uneven
• Forecasting how many agents a workload needs

Coordinate groups of AI agents in the cloud with Flow Nexus. Assign research or development tasks, automate workflows triggered by events or schedules, and monitor execution, queues, and agent capacity through the platform's tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Split research and analysis across multiple agents
• Coordinate development across repositories
• Automate testing, builds, and deployment

Find marketing ideas for a SaaS or software product based on its stage, audience, budget, and team. Draw from 139 ideas to shortlist relevant options, with starting steps, expected outcomes, and resources needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding new ways to promote a software product
• Choosing marketing tactics on a limited budget
• Exploring promotion ideas before launch

Simulate lithium-ion battery charging, discharging, and rest with PyBaMM. Track voltage and capacity, record parameter sources, check how numerical settings affect predictions, and compare simulated curves with measured cycling data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Predicting voltage changes during charge, discharge, and rest
• Comparing simulation results with measured cycling data
• Checking how numerical settings affect predictions