ark-chainsaw-testing
Run and write Ark Chainsaw tests with mock-llm. Use for running tests, debugging failures, or creating new e2e tests.
409 repo starsObserved in 2 repos
Testing & Quality
Testing & Quality skills
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Ark Dashboard and UI Testing
Test the Ark Dashboard and UI with Playwright and create PRs with screenshots. Use this skill when testing dashboard UI, taking screenshots for PRs, or validating dashboard changes.
409 repo starsObserved in 2 repos
Testing & Quality
dial9-diagnose-long-poll
Root-cause why a poll was long, not just where it was. Use after `red_flag_scan.js` or `analyze.js` flags a long poll and you need to explain it and recommend a fix — including the off-CPU case with no scheduling events captured. Use when the user says "why is this poll long", "what is it blocked on", "is something holding a lock", or "off-CPU but no sched events".
409 repo starsObserved in 1 repos
Testing & Quality
dial9-red-flags
Automated health checks for dial9 Tokio runtime traces. Detects long polls, task leaks, scheduling delays, blocking calls, queue buildup, worker imbalance, CPU contention, and span anomalies. Use when you want a quick automated assessment of trace health.
409 repo starsObserved in 1 repos
Testing & Quality
dial9-runtime
Tokio async runtime internals reference. Covers the execution model, waking and scheduling, cooperative scheduling, poll duration effects on tail latency, worker parking, and how to connect trace data to application behavior. Use when reasoning about runtime performance from first principles.
409 repo starsObserved in 1 repos
Testing & Quality
dial9-s3-analysis
Analyze dial9 Tokio runtime traces stored in S3 buckets. Use when a user provides an S3 bucket containing dial9 traces and wants to understand runtime behavior, diagnose performance issues, or explore what data is available.
409 repo starsObserved in 1 repos
Testing & Quality
dial9-toolkit
JavaScript analysis toolkit for parsing and analyzing dial9 Tokio runtime traces. Always start trace diagnosis with analyzeTraces() from analyze.js, then use parseTrace() and lower-level helpers only to confirm assumptions or drill into raw events.
409 repo starsObserved in 1 repos
Testing & Quality
dial9-trace-analysis
Analysis pipeline API for dial9 traces. Covers analyzeTraces() aggregation, buildWorkerSpans, attachCpuSamples, scheduling delays, flamegraphs, span data, and the full return schema. Use when analyzing parsed traces or building custom analysis pipelines.
409 repo starsObserved in 1 repos
Testing & Quality
dial9-trace-recipes
Diagnostic recipes for common questions about dial9 Tokio runtime traces. Covers finding long polls, task leaks, worker utilization, blocking calls, wake chains, span analysis, task dumps, time-window debugging, and estimating allocation totals from sampled `Alloc` events. Use when answering specific diagnostic questions about trace data.
409 repo starsObserved in 1 repos
Testing & Quality
dial9-zoom-window
Zoom into a narrow time window of a dial9 trace to see every worker and OS thread at one moment. Use after an aggregate pass (`analyze.js`, `red_flag_scan.js`) flags a timestamp — a long poll, a queue spike, a latency outlier. Use when the user says "zoom in", "what was happening at +6953ms", or "show me the window around that poll".
409 repo starsObserved in 1 repos
Testing & Quality