Results for “experiment tracking”

Plan A/B tests to compare page changes using clear hypotheses and meaningful measures. The skill helps define sample size, duration, traffic allocation, and result interpretation, and organize a continuing program of prioritized experiments.

• Compare headlines or signup buttons
• Estimate test sample size and duration
• Interpret results and possible adverse effects

Track machine learning experiments with SwanLab by recording training settings, metrics, and media such as images and audio. Learn to compare runs, inspect training charts, and connect existing training code to local, cloud, or self-hosted dashboards.

• Comparing experiments with different training settings
• Viewing training metrics in a local dashboard
• Logging sample images and audio alongside metrics

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

The English summary is being prepared. Showing the original description.

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

The English summary is being prepared. Showing the original description.

Organize experiment photos, audio, and notes into Markdown logs with structured metadata. Assign experiment and sample batch IDs, archive original attachments, and optionally connect records to Feishu group messages or an Obsidian notebook.

• Turning experiment photos and voice notes into consistent logs
• Tracking the same sample batch across multiple experiments
• Archiving original files with links from experiment logs

Set up W&B to record machine learning metrics and settings, visualize training progress, and compare experiments. Includes automated searches for training settings, version tracking for datasets and models, and shared reports for team collaboration.

• Recording and visualizing training metrics
• Comparing experiments with different training settings
• Automatically searching for better training settings

Manage machine learning experiments with MLflow by recording settings, metrics, files, and trained models. Covers experiment comparison, model version management, reproducible project configurations, and deployment workflows across local and cloud environments.

• Recording experiment settings and evaluation results
• Comparing model performance across experiments
• Managing model versions for production use

Use W&B to record machine learning experiments, visualize training, and compare results. The skill also covers automated searches for training settings and version tracking for datasets and models, helping teams share experiments and trace their inputs.

• Logging training metrics and viewing progress in real time
• Comparing experiments with different training settings
• Searching automatically for better training settings

Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.

• Comparing landing page headlines
• Testing signup button changes
• Planning pricing page experiments

Launch machine learning training jobs on local or remote GPUs. The skill checks available GPU memory, synchronizes code, saves logs, and verifies startup, with optional experiment tracking and support for Vast.ai and Modal.

• Launch training on an available remote GPU
• Run experiments locally with CUDA or MPS
• Record training metrics with W&B

Build machine learning workflows that connect data checks, training, evaluation, and deployment. The skill implements experiment tracking, model version management, and automated retraining, with reproducible environments and explicit validation thresholds before models enter production.

• Automate model training and retraining workflows
• Record and compare machine learning experiments
• Build a feature store for model input data

Plan A/B tests that compare page or product changes, with clear hypotheses, sample sizes, success metrics, and traffic allocation. Get a structured test plan and guidance for interpreting results and deciding what to try next.

• Comparing signup button copy
• Planning a pricing page experiment
• Estimating sample size and test duration

Use MLflow to record machine learning experiments, compare results, and manage model versions. The skill covers logging training settings, metrics, and files, organizing a model registry, and preparing models for local or cloud deployment.

• Comparing training settings and model performance
• Recording experiments for later reproduction
• Managing model versions and release stages

Route product questions to a specialist for prioritization, research, analytics, experiments, or implementation. Support recurring discovery by tracking interviews and assumption tests, checking how customer needs connect to proposed solutions, and returning results with a concise digest.

• Prioritizing features with an explicit framework
• Planning product experiments and sample sizes
• Tracking weekly interviews and assumption tests

Plan and analyze A/B tests, prepare tabular data, and train and evaluate prediction models. Estimate intervention effects from observational data, track model experiments with MLflow, and translate statistical findings into business decisions.

• Planning A/B test sample sizes and analyzing results
• Preparing tabular data for prediction models
• Comparing model performance and recording experiments

Machine learning experimentation reference for model-experimentation conventions, experiment tracking and reproducibility, dataset and model abstractions, ML engagement fundamentals, and model-production readiness. Use when standing up ML experimentation infrastructure or assessing whether a trained model is ready for production.

The English summary is being prepared. Showing the original description.

Use TensorBoard to visualize training loss and accuracy, compare experiments, and inspect model structure. Guides logging for PyTorch and TensorFlow, including weight distributions and performance profiling to investigate training problems and processing bottlenecks.

• Monitoring training loss and accuracy
• Comparing experiments with different training settings
• Inspecting weight and gradient distributions

Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO, marketplace integration, and ML observability. Triggers: "Weights and Biases", "W&B", "WeightsAndBiases", "ML experiment tracking", "model registry", "experiment management", "wandb".

The English summary is being prepared. Showing the original description.

Add file-based observability, tracing, and run analysis to LLM/agent experiments — per-turn transcripts, tool calls and results, reasoning traces, token/cost accounting, per-episode artifacts, plus terminal viewers and a run-comparison report. Platform-agnostic: one small adapter covers OpenAI, Gemini/Vertex, Anthropic, LiteLLM, Tinker, vLLM, or any custom inference stack, and the same tooling then works unchanged. Use this skill whenever the user wants observability, tracing, logging, or run tracking for model experiments; asks why an agent failed a task or wants to replay/debug/diff an episode; wants to compare models, arms, or ablations; wants to instrument a new folder, repo, or platform ("add observability here", "do the same for Tinker/Gemini/OpenAI"); wants to import or tie in existing experiment results so old runs show up alongside new ones; or wants eval runner scripts where many models share one protocol. Reach for this even when they only say "log what the model is doing", "I can't tell what happened in this run", or "set up traces for this experiment".

The English summary is being prepared. Showing the original description.

Expert guidance for Comet ML, the platform for tracking machine learning experiments, managing models, and monitoring production ML systems. Helps developers log experiments, compare model versions, and build reproducible ML pipelines with automatic code/data versioning.

The English summary is being prepared. Showing the original description.

Measure what matters. Event tracking design, attribution modeling, funnel analysis, experimentation platforms. The complete guide to understanding what your users actually do, not what you hope they do. Good analytics is invisible until you need it. Then it's the difference between guessing and knowing. Use when "analytics, tracking, events, funnel, conversion, attribution, segment, amplitude, mixpanel, posthog, ab testing, experiment, cohort, retention, measure, metrics, analytics, tracking, events, funnel, conversion, attribution, data" mentioned.

The English summary is being prepared. Showing the original description.

Track and optimize agent specialization during methodology development. Use when agent specialization emerges (generic agents show >5x performance gap), multi-experiment comparison needed, or methodology transferability analysis required. Captures agent set evolution (Aₙ tracking), meta-agent evolution (Mₙ tracking), specialization decisions (when/why to create specialized agents), and reusability assessment (universal vs domain-specific vs task-specific). Enables systematic cross-experiment learning and optimized M₀ evolution. 2-3 hours overhead per experiment.

The English summary is being prepared. Showing the original description.

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.

The English summary is being prepared. Showing the original description.

Run repeated code improvement experiments with multiple agents. It plans and reviews candidate changes, compares benchmark results, merges candidates that pass rechecking, and records progress until a target, iteration limit, or another stopping condition is reached.

• Comparing several code improvement ideas with benchmarks
• Running repeated experiments toward a measurable target
• Tracking candidate scores and experiment history