'arize' 검색 결과

Use when recurring process failures, obsolete rules, or an explicit user request call for harness improvement.

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

Use when independent tasks benefit from parallel work without shared state or sequential dependencies

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

Use when continuing implementation from an existing plan

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

Use when verified implementation is ready for an integration decision or authorized integration

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

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

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

Use when arranging the project quality-check or investigating a concrete unresolved code concern

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

Use when independent bounded tasks benefit from delegation during implementation

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

Use when implementing any feature or bugfix, before writing implementation code

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

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

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

Use when selecting skills for a task or resolving how skill workflows apply

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

Use when a multi-step change needs explicit sequencing, dependencies, or a handoff

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

Use when creating new skills, editing existing skills, or verifying skills work before deployment

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

10 product agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. PM toolkit (RICE), agile PO, product strategist (OKR), UX researcher, UI design system, competitive teardown, landing page generator, SaaS scaffolder, research summarizer. Python tools (stdlib-only).

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

Monitor a build process (webpack, turbo, docker) for warnings and errors as they stream. Summarize issues and fix them before the build finishes.

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

Focused Signals scout for PostHog projects running Replay Vision scanners — the standing LLM probes that watch session recordings and write `$recording_observed` events. Watches two promises: that enabled scanners are actually observing (throughput / success-rate cliffs, exhausted quota — a silent watch gap), and that what the scanners see in aggregate gets surfaced (a monitor's `yes`-rate or a scorer's score stepping away from its own baseline, a classifier tag or a recurring summarizer theme concentrating across many sessions). It is the agentic pull complement to the per-session push path: scanners with `emits_signals` already emit one signal per session into this same inbox, so this scout never repeats them — it adds the cross-session shape the per-session probe can't see. Emits findings only when they clear the confidence bar; otherwise writes durable memory and closes out empty. Self-contained peer in the signals-scout-* fleet.

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

Guides agents through creating and safely sizing a Replay Vision scanner: choosing the scanner type (monitor/classifier/scorer/summarizer), shaping the RecordingsQuery that selects sessions, and — crucially — estimating observation volume and checking the org's monthly quota before creating, so a broad scanner doesn't exhaust the budget on its first scheduled sweep. TRIGGER when: user asks to create, set up, or configure a Replay Vision scanner, OR when you are about to call vision-scanners-create, OR when widening an existing scanner's query or sampling_rate via vision-scanners-update. DO NOT TRIGGER when: only reading scanners or observations, deleting a scanner, or running an existing scanner against a single session on demand (vision-scanners-scan-session).

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

Finds the most informative session recording linked to an error tracking issue. Use when a user has an error tracking issue ID and wants to watch a replay showing what the user was doing when the error occurred. Ranks linked sessions by recency, activity score, and journey completeness, then summarizes the pre-error context. Replaces blind session picking from potentially hundreds of linked recordings.

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

Assesses what a page's heatmap is telling you and recommends concrete changes. Pulls click / rageclick / scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements. TRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap/click data, or to 'analyze/assess/review the heatmap' for a URL. DO NOT TRIGGER when: the user only wants to create a saved heatmap screenshot with no analysis (use heatmaps-saved-create directly), or is asking about session replay in general (use investigating-replay).

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

Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).

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

Builds diagnostic and prognostic classifiers on omics feature matrices with regularized logistic regression, random forest, and gradient-boosted trees, handling the p>>n regime, batch shortcut learning, class imbalance, and probability calibration. Use when building a classifier from expression, methylation, or variant data, choosing an algorithm for high-dimensional small-n data, or diagnosing a suspiciously perfect AUC. For unbiased evaluation see machine-learning/model-validation; for feature selection see machine-learning/biomarker-discovery; for time-to-event outcomes see machine-learning/survival-analysis.

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

Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.

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

Creates and edits CARLA Leaderboard route files — placing waypoints and scenario trigger points interactively from the spectator camera (route_creator, scenario_creator), visualising an existing route in the simulator (route_displayer), summarising it as a table (route_summarizer), capturing the current weather in route format (weather_creator), sorting scenarios by route position (scenario_orderer) and converting 1.0-format routes to 2.x (route_bridge). Use when the user asks to "make a new route", "add a scenario to a route", "visualise/debug a route", "see what's in this route file", or "convert old leaderboard routes".

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

DON'T USE THAT SKILL. IT'S JUST AN EXAMPLE. Summarize today's Gmail inbox by category with anonymized senders and subjects, then surface the top 3 emails to focus on next. Run only when the user types /email-summary.

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