1.7천건 · 관련도순
Analyze gh-aw execution traces, which record individual processing steps, to investigate slow or failing workflows. Using local JSONL files or telemetry backends, the skill checks timing, errors, missing attributes, and trace connections to support focused improvements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Test APIs and forms with unexpected input to uncover error responses that expose internal details. The skill checks response bodies for stack traces, server paths, and library information, preserving specific evidence rather than treating every server error as a vulnerability.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Assess classic ASP.NET applications for security weaknesses in ViewState, the data used to preserve page state, exposed logs, error details, and service endpoints. Organize evidence and separate observed weaknesses from demonstrated impact when preparing findings.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Add OpenTelemetry tracing to frontend and backend flows. Connect execution records across services and background jobs, record phase durations and entity IDs, and mark failures so developers can investigate slow or broken operations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Automatically send Claude Code conversations and tool calls to Braintrust. View nested activity records that connect each session, conversation exchange, and operation, including file reads, edits, and terminal commands, to inspect how coding work unfolded.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Record and replay a program with rr to investigate crashes and AddressSanitizer memory errors. Step backward through execution, inspect variables and memory, and extract the sequence of operations leading to a failure.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Record function entry and exit in C/C++ programs, with separate logs for each thread. Convert those logs into a Perfetto timeline to inspect call depth, execution order, and activity across threads.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate slow interactions and rendering using performance traces, which record execution events, alongside source code. Identify the responsible code, distinguish measurements from hypotheses, and guide fixes that preserve behavior, with tests and comparable recordings for verification.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Record network activity, console errors, screenshots, and page HTML alongside an existing browser automation run. Organize the captured events into searchable files for each page, making it easier to investigate failures and review what happened.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI/CD quality gates, observability, or cost optimization. Triggers on: "evaluate my agent", "add evaluator", "measure quality", "quality gate", "run evals", "agent too slow", "why is it slow", "reduce latency", "set up observability", "CloudWatch dashboard", "how much does my agent cost", "cost optimization", "logs not showing up", "logs missing", "spans not found", "eval failing", "eval error", "dev traces", "local traces", "agentcore dev traces", "traces to CloudWatch". Not for debugging errors or crashes — use agents-debug. Slow but correct routes here; broken routes to debug.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use `pvanalyze` to inspect existing .NET `.nettrace` files from the command line, including GC, JIT, CPU stacks, allocation, DATAS, events, exceptions, timeline, and call-tree analysis with JSON or SpeedScope. USE FOR: the user mentions pvanalyze, PerfView-style CLI trace analysis, or cross-platform .nettrace inspection; the task starts from an existing .nettrace file and needs. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn any source that describes how a kind of task gets done (a SKILL.md, a chat log, a runbook, plain prose) into a runnable Morph trace. Lift it into a DAG, write a contract per step, place inputs, and drive the full run lifecycle to verify it. Use whenever someone wants to make a trace from a source.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to run a binary, trace execution, or observe runtime behavior. Runtime analysis via QEMU emulation, GDB debugging, and Frida hooking - syscall tracing (strace), breakpoints, memory inspection, function interception. Keywords - "run binary", "execute", "debug", "trace syscalls", "set breakpoint", "qemu", "gdb", "frida", "strace", "watch memory"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures. Use this skill when you need to reproduce a bug, capture execution traces for debugging, instrument code to record program behavior, generate replay scripts for bug reproduction, diagnose hard-to-reproduce failures, or perform deterministic replay of program execution. Triggers when users ask to instrument code for tracing, capture execution traces, reproduce bugs, generate replay scripts, or enable deterministic debugging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Think and work like an expert Chemical Oceanographer. Use when a task calls for Chemical Oceanographer judgment. Reasons from seawater thermodynamics, carbonate-system coupling (DIC, TA, pH, pCO2), redox hierarchies, and tracer conservation on density surfaces through CO2SYS/seacarb with Dickson CRMs, Winkler oxygen, IRMS isotopes, GO-FLO clean trace-metal sampling, and GLODAP/SOCAT/GEOTRACES synthesis while treating organic alkalinity, headspace equilibration, pCO2-mooring biofouling, and trace-metal contamination as first-class failure modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run trace-mcp security, quality-gate, and antipattern checks before committing or opening a PR. Activate when the agent is about to create a commit or pull request in a project indexed by trace-mcp.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use trace-mcp tools for code navigation, impact analysis, and framework-aware queries instead of Read/Grep/Glob/Bash. Activate whenever the agent needs to explore, understand, or modify a codebase that has trace-mcp indexed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Mine a per-kernel optimization trace — a git repository capturing successive versions of one kernel being optimized — into structured, gate-validated optimization-experience records for the GPU kernel wiki. Use when asked to distill an optimization run, a kernel_opt trace directory or a version ladder into wiki records; to report what such a run actually achieved; to build, extend, re-run or validate the staging store behind those records; or to explain how a trace-derived record's number, snippet or provenance was established.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze production Agentforce agent behavior using session traces and Data Cloud, and manage Agent Health Monitoring (AHM) alerts. TRIGGER when: user queries STDM session data or Data Cloud trace records; investigates production agent failures, regressions, or performance issues; asks about session traces, conversation logs, or agent metrics; wants to reproduce a reported production issue in preview; runs findSessions or trace analysis queries; creates, lists, updates, or deletes an AHM data alert on an agent metric (escalation rate, deflection, etc.); asks why an alert is not firing or wants to check whether alerts have fired (notification counts, or the per-alert Incidents view). DO NOT TRIGGER when: user creates, modifies, or debugs .agent files during development (use agentforce-generate); writes or runs test specs (use agentforce-test); uses sf agent preview for local development iteration; deploys or publishes agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
按 TRACE 框架（Trust / Reliability / Adaptability / Convention / Effectiveness，5 维 15 子项）评测 Skill 包质量。当用户说『用 TRACE 评测』『评一下这个 skill』『skill 质量打分』『五维度评测』『帮我评估这个技能包』『TRACE evaluation』等需要给 Skill 打分出报告时使用本技能。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
当用户想使用 HiAgent 观测(observe)能力（API Token、Trace Spans 查询）时，务必使用这个技能给出可直接执行的 cli-anything-hiagent observe 命令与排障步骤。尤其适用于用户提到 agent-harness、cli_anything、--json、workspace-id、custom-app-id、VOLC_ACCESSKEY/VOLC_SECRETKEY、observe token、observe trace，以及希望用命令行(cli-anything-hiagent / python -m cli_anything.hiagent_sdk)。trace-ai-process / trace-ai-history / alert-ai-process / RuleID / IsStream
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Jaeger provider for obz. Covers trace search, trace retrieval by ID, and extension commands for service and operation discovery. This skill should be used when the user mentions "Jaeger", "obz trace -p jg", or needs to search distributed traces from a Jaeger backend.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes API call traces from a sandbox or API monitor (JSON) to group calls by category, reconstruct high-level behaviors (process injection, file drops, network, crypto), and flag suspicious call sequences. Activates for requests to analyze an API trace, interpret sandbox API logs, or identify behavior from Win32/Native API calls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The investigation harness for "why is this slow?" over a Pulp Perfetto trace (.pftrace). Runs the hypothesis→query→drill-down chain-of-evidence loop autonomously and returns a plain-English root cause + evidence + a concrete fix. TRIGGER on "why is my plugin slow to open", "find the slowest frames", "why is the UI stuttering", "why is my plugin using so much CPU", "which DSP node is expensive", "the load meter looks calm but CPU is pinned", or a named `pulp trace gpu-startup|gpu-health|gpu-probe` analysis. Ships Pulp-specific hints for dsp, frame, js, gpu, and cross-platform symptoms.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.