'slo' 검색 결과

Analyzes Google Cloud BigQuery slot consumption, query costs, and execution bottlenecks using INFORMATION_SCHEMA. Use when diagnosing slow BigQuery queries, slot starvation, high on-demand query costs, unpartitioned table scans, or join performance issues. Don't use for generic BigQuery administration (use bigquery-basics), BigQuery ML (use bigquery-ai-ml), or DataFrame operations (use bigquery-bigframes).

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

Catalog-then-fix slop removal on an existing prose draft. Parallel catalog subagents inventory four slop categories (theatrics, overwrought register, corrective antithesis, dramatic short sentences), fix subagents repair only what a catalog names, mechanical lint + frequency analysis bracket the run, and a regression gate (lint delta, word count, cold meaning check) decides whether the result ships. Use when the user says "deslop this draft", "catalog deslop", "strip the AI patterns from this file", or as the final stage of the article-factory and mosaic-writing skills. For writing or redrafting prose from scratch, use the prose skill instead - this skill only repairs an existing draft in place.

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

Use before finishing a change, or when asked to clean up, review for slop, drift, stale docs, or duplicated rules — runs the deterministic unslop lint and, for prose-level slop, delegates to the unslop-reviewer agent.

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

Agent fallback for CEngineServer_IsLogEnabled (auto-generated, category: func). Locate CEngineServer_IsLogEnabled in the CS2 engine module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CEngineServer_IsLogEnabled, CEngineServer_IsLogEnabled

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

화면 표시, API, 데이터베이스의 지연을 측정해 원인을 좁히고 개선 전후 수치로 효과를 확인합니다. 효과 없는 변경의 되돌리기와 성능 저하를 막는 감시까지 안내합니다.

• 페이지 표시와 조작 지연의 원인을 조사합니다
• API 지연과 반복 쿼리를 줄입니다
• 변경 후 성능 저하를 확인합니다

Investigate slow SQL using execution plans, which show how a database processes a query. Review indexes, filters, joins, and maintenance practices through PostgreSQL examples to identify bottlenecks and plan changes to queries or database structure.

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

• Investigating slow SQL queries
• Reviewing index choices and column order
• Reading EXPLAIN execution plans

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

Deploy decoy files and monitor changes, renames, and deletions for early signs of ransomware. This skill guides Python monitoring, email, Slack, and syslog alerts, plus simulated file operations to verify that the detection and notification pipeline works.

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

• Monitoring shared drives and NAS for suspicious file changes
• Adding decoy file monitoring alongside endpoint protection
• Testing incident response with decoy file triggers

Design service monitoring dashboards and improve existing alert configurations. Generate Grafana dashboard files and documentation, analyze noisy or duplicate alerts and coverage gaps, and outline how metrics, logs, and request traces fit together.

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

• Designing monitoring for a new service
• Reducing noisy and duplicate alerts
• Creating Grafana dashboards for different roles

Investigate failing or slow BigQuery jobs and unexpected cost increases. Compare execution details and resource usage with a normal baseline to isolate bottlenecks, identify likely causes, and determine practical remediation steps.

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

• Investigate failed or slow BigQuery jobs
• Locate bottlenecks in execution stages
• Diagnose sudden increases in query or capacity costs

Measure and improve animation performance on frontend pages. Identify offscreen activity, pause CSS and canvas or WebGL loops, audit resource cleanup, and compare runtime observations before and after changes to investigate scrolling issues and long-session slowdowns.

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

• Pause animations outside the viewport
• Investigate jerky scrolling
• Audit cleanup after page navigation

Review and improve UI accessibility, including color contrast, keyboard operation, visible focus, and clear status messages. A contrast checker supports color checks, while guidance also covers text zoom and form fields obscured by mobile keyboards.

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

• Checking contrast between text and background colors
• Improving keyboard navigation and visible focus
• Clarifying empty, loading, and error states

Build or review website and app interfaces with choices grounded in the product’s identity and purpose. Covers colors, layouts, decoration, dashboard content, and working controls, with concrete guidance for replacing repetitive design patterns.

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

• Reviewing a landing page for repetitive layouts
• Choosing colors and decoration that fit a brand
• Reworking dashboard charts, tables, and empty states

Edit headlines, marketing copy, and product text into clear, concrete prose. Provides examples for removing empty claims, repetitive phrasing, and excessive formatting while preserving the writer’s voice and avoiding invented facts.

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

• Rewriting vague headlines and product descriptions
• Editing repetitive phrasing in AI-written drafts
• Checking claims, figures, and testimonials against source material

Clean up code comments without changing executable code. The skill removes obvious explanations, decorative headings, and vague notes while preserving concise comments about intent, constraints, security, edge cases, and other information the code does not show.

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

• Removing comments that merely repeat the code
• Simplifying decorative headings and lengthy notes
• Preserving explanations of design decisions and constraints

Apply purpose-based checks while building an interface, or audit an existing project with prioritized findings. Reviews visual choices, content, working interactions, and evidence for claims while requiring a clear design direction.

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

• Applying design checks while building a new interface
• Auditing an existing site with prioritized findings
• Reviewing whether visual choices serve a clear purpose

Diagnose and improve slow web interfaces by measuring loading, rendering, interactions, and animations. The skill addresses images, JavaScript bundles, page layout, and network requests, then compares before-and-after results to verify improvements across devices and connection speeds.

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

• Reducing slow initial page loads
• Improving sluggish scrolling and animations
• Reducing image and JavaScript download sizes

[omh] Postmortem for an outage or SLO miss: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence. Use when the user says: reliability-review, reliability review, incident review, incident postmortem, postmortem, post-mortem, slo review, slo.

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

[omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical. Use when the user says: ai-slop-cleaner, cleanup, deslop, refactor, risky, behavior-preserving refactor, risk analysis, refactor workflow.

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

Model-guided autonomous root-cause analysis over a UModel object-graph semantic layer. Use with `umodel-query` when diagnosing service degradation, SLO breach, latency/error spikes, incidents, outages, or questions like why a service is slow, degraded, erroring, or timing out. The skill guides evidence collection across object graph, metrics, logs, topology, runbooks, deployments, config changes, business traffic, and runtime capacity; it is especially useful for ruling out red herrings such as recent but unrelated deployments. Triggers: root cause, RCA, incident, SLO breach, outage, postmortem, latency spike, error spike, timeout, 根因分析, 故障排查, 告警定位, 为什么慢, SLO 击穿.

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

Use when the user wants to humanize text, trim slop, de-AI or de-slop writing, remove AI tells, fix robotic or ChatGPT-sounding prose, or make writing sound human and natural. Also run before delivering a CV, cover letter, email, report, or essay to be sent. Removes 71 documented AI-writing patterns with a local detector, preserves numbers, names and citations, and rebuilds toward a human voice rather than a flat husk. Mode-aware, so it never fabricates voice on factual content.

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

Edit drafts into natural prose, inspect AI-sounding patterns, or review how a specified audience might respond passage by passage. Zero Slop runs inside the user's existing AI assistant with local tools that protect source details. Use for humanizing or de-slopping writing, polishing outward-facing prose, social drafts, final editorial checks, or an explicit simulated reader review. Preserve facts, voice and format; reader simulations are hypotheses, not human feedback.

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

Suede Slop Stop: Suede Labs context-aware anti-slop pass for finished prose. Find or remove generic filler, manufactured emphasis, false agency, formulaic structure, chat and draft residue, and formatting applied by rule, without flattening the author's voice. Use before copy, a README, an email, a social post, or a doc ships; after a long assisted-writing session; or for a findings-only slop audit. NOT FOR: writing new copy (use suede-copy); deciding whether a person or model wrote text; changing or certifying facts, which require primary evidence.

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

Review code for AI slop patterns. TRIGGER when user says "review for AI slop", "check for AI patterns", "clean up AI code", "audit AI-generated code", or "review AI slop".

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