'usage' 검색 결과

Diagnose frozen or slow Qwen Code sessions on the current machine by checking CPU and memory usage, process states, child processes, network connections, and debug logs. Receive a diagnostic report with suggested next steps, without stopping processes.

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

• Investigating an unresponsive Qwen Code session
• Diagnosing a specific process by PID
• Checking high CPU or memory usage

Retrieve BigQuery execution records and resource metrics using the right tool for each task. The skill guides monitoring tool selection and SQL queries for performance investigations, capacity analysis, and reviews of billable compute and storage usage.

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

• Retrieve execution details for a slow job
• Check compute capacity contention and queue delays
• Review reserved capacity and autoscaling limits

Prepare quarterly business reviews using account records from HubSpot and usage trends from Postgres. Create a draft slide deck and supporting document for each due account, with traceable figures, support issues, and evidence-backed expansion opportunities.

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

• Prepare quarterly reviews for accounts due soon
• Review declining usage and important support issues
• Gather supporting data for customer discussions

Combine product usage, support issues, payment status, and renewal dates to rank accounts by churn risk, meaning the risk of cancellation. Produce a Slack list with specific evidence and a suggested next action for each account.

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

• Reviewing accounts at risk of cancellation each day
• Prioritizing outreach before contract renewals
• Understanding why an account received a high risk rating

Find quotes that fit a text’s themes, with attribution and a short reason for each suggestion. Add sourced quotes, research thinkers, and organize a quote collection by theme and usage history to avoid repetition.

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

• Finding a fitting quote for a newsletter
• Saving sourced quotes without duplicates
• Researching a thinker’s quotes by theme

Operate an opencodex proxy, which acts as an intermediary for AI service requests. Use CLI commands to inspect configuration, manage accounts and models, review request routing, and check usage and runtime health.

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

• Check proxy readiness and diagnose connection problems
• Review provider settings and available models
• Inspect account selection and request routing

Use Memori through MCP, a protocol connecting agents to tools, to retrieve past decisions and preferences, summarize ongoing work, and resume after conversation compression. It also guides selective long-term memory storage and usage limit checks.

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

• Retrieve decisions and preferences from earlier sessions
• Review current work when starting a session
• Resume work after conversation context is compressed

Manage Cloudinary images, videos, and files with natural language requests. Organize folders, configure upload rules, inspect assets, generate transformed versions, and check storage and bandwidth usage through Rube MCP and Composio.

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

• Organizing campaign assets into folders
• Setting upload rules for product images
• Generating cropped images and thumbnails

Automate Anthropic Admin tasks involving API keys, usage, workspaces, and organization management through Rube MCP, a connection to external tools. The skill guides tool discovery, connection checks, multi-step workflows, and bulk operations.

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

• Manage Anthropic Admin API keys
• Check Anthropic usage
• Handle workspace and organization management tasks

Check estimated token usage against daily limits before and after each automated loop run. Switch to reporting only, exit early when required, and record run outcomes so repeated agent work stays within configured limits.

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

• Checking daily token usage before a run
• Switching to reporting only near budget limits
• Exiting early when there is no actionable work

Evaluate local Codex skills and plugins, understand their scores, and identify fixes to prioritize. Get explanations of token estimates, set up benchmark scenarios, and prepare workflows for measuring actual token usage.

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

• Evaluate a local skill or plugin
• Understand scores and prioritize fixes
• Explain token estimates and prepare actual measurements

Launch a terminal or web dashboard to inspect Claude Code activity across projects. Browse sessions, search messages, track token usage and estimated costs, and check MCP servers that connect external tools to the agent.

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

• Checking daily usage and estimated costs
• Searching past conversations across projects
• Investigating MCP server status

Locate function and class definitions, usages, and relevant files with ripgrep, using text patterns and file filters. Search Git history to see when text appeared or disappeared and investigate who changed specific lines.

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

• Finding function or class definitions
• Locating usages of a particular function
• Narrowing searches by file type or path

Migrate .NET Framework code that forcibly stops threads to cooperative cancellation, where work checks and responds to stop requests. The skill covers loops, timeouts, blocked threads, and ASP.NET request endings, with cleanup and validation guidance.

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

• Replacing Thread.Abort when moving to .NET 6 or later
• Migrating timeouts and blocked-thread cancellation
• Preserving cleanup from ThreadAbortException handlers

Review mock configurations in .NET tests by tracing the production code each test exercises. Identify unused, unreachable, duplicated, or replaceable setups, explain concrete fixes, and distinguish them from appropriate mocks for databases, HTTP clients, and other external services.

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

• Finding unused or unreachable mock setups
• Consolidating duplicated mock configurations
• Reviewing ILogger and IOptions replacements

Investigate code with the lsp tool, which uses a language server to understand names, imports, and types. Find definitions and usages, inspect signatures and file outlines, and check compiler or type errors after edits.

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

• Finding where a function or variable is defined
• Tracing symbol usages across imports and aliases
• Reading type signatures and documentation

Optimize Apollo.io costs and credit usage. Use when managing Apollo credits, reducing API costs, or optimizing subscription usage. Trigger with phrases like "apollo cost", "apollo credits", "apollo billing", "reduce apollo costs", "apollo usage".

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

Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating customers, contracts, or rate cards, designing billable metric group keys, managing credits and commits, configuring invoicing, syncing invoices with Stripe Billing, billing AI applications for token usage, setting up self-serve (PLG) pricing, reviewing customer health, commit burn, portfolios, or renewals, or migrating from Stripe Billing Meters to Metronome.

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

Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating customers, contracts, or rate cards, designing billable metric group keys, managing credits and commits, configuring invoicing, syncing invoices with Stripe Billing, billing AI applications for token usage, setting up self-serve (PLG) pricing, reviewing customer health, commit burn, portfolios, or renewals, or migrating from Stripe Billing Meters to Metronome.

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

Analyze Claude Code usage trends over time using the Agent Monitor's analytics API — daily session counts, daily event counts, token volumes by type, model distribution, tool usage rankings, and agent/event type distributions across 365-day retention windows.

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

Use when answering Scenario admin analytics questions about Creative Unit consumption, most-used models, usage by user or project, AI adoption observability, cached usage data, CSV exports, enterprise PDF reports with charts, or a local analytics dashboard. Keywords: usage API, CU, analytics, adoption, reporting, consumption, cache.

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

Generates user-facing usage statistics, activity summaries, and personalized insights dashboards (weekly recaps, year-in-review, Spotify Wrapped-style). Use when user wants to show usage stats, activity insights, or shareable recap screens. Different from analytics-setup which sends data to a backend — this shows insights to the USER on-device.

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

Audits .NET test mock usage by tracing each mock setup through the production code's execution path to find dead, unreachable, redundant, or replaceable mocks. Use when the user asks to audit mock usage, find unused or unnecessary mock setups, check if mocks are needed, reduce mock duplication or over-mocking, simplify test setup, or review whether mock configurations like ILogger/IOptions should use real implementations instead. Supports Moq, NSubstitute, and FakeItEasy.

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

Guides migration of .NET Framework Thread.Abort usage to cooperative cancellation in modern .NET. USE FOR: modernizing code that calls Thread.Abort, catching ThreadAbortException, replacing Thread.ResetAbort, replacing Thread.Interrupt for thread termination, resolving PlatformNotSupportedException or SYSLIB0006 after retargeting to .NET 6+, migrating ASP.NET Response.End or Response.Redirect(url, true) which internally call Thread.Abort. DO NOT USE FOR: code that only uses Thread.Join, Thread.Sleep, or Thread.Start without any abort, interrupt, or ThreadAbortException usage — these APIs work identically in modern .NET and need no migration. Also not for projects staying on .NET Framework, or Thread.Abort usage inside third-party libraries you do not control.

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