logs

Locate and search remote ML experiment logs for errors and progress.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kang-jaehyun/Mac-the-researcher --skill logs-kang-jaehyun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logs
Source: https://github.com/kang-jaehyun/Mac-the-researcher/tree/main/.claude/skills/logs
Command: npx skills add https://github.com/kang-jaehyun/Mac-the-researcher --skill logs-kang-jaehyun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Anomaly diagnosis and monitoring of ML experiments requires fast access to log outputs across multiple remote clusters; this skill provides a unified interface to locate, tail, and search logs from training runs to speed debugging and progress assessment.

Core Features & Use Cases

  • Retrieve logs for a specific job_id or experiment to inspect training output and errors.
  • Tail, search, and filter logs with patterns (e.g., ERROR, Exception, Traceback) across clusters.
  • Monitor recent progress by viewing live or recent log entries from running experiments.

Quick Start

Ask the AI to fetch logs for a specific job_id or experiment across your remote clusters.

Frequently Asked Questions about logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I view and search remote experiment logs for ML training errors?

The logs skill locates and reads remote ML experiment logs to diagnose training progress and errors, allowing you to tail, search, and filter log outputs from per-job or per-experiment runs across multiple remote clusters.

Can I tail live log entries from running training jobs across remote clusters?

Yes, you can tail live or recent log entries from running experiments across remote clusters using the tail_log tool, allowing you to monitor recent training progress and diagnose anomalies in real-time.

What is the best way to locate a specific job_id log output in a remote cluster?

To locate a specific job_id log output in a remote cluster, use the find_logs tool to search remote log stores, which retrieves the exact training run output needed for progress assessment and debugging.

Are there limitations when using grep to search large remote training logs?

Limitations depend on remote log store access and cluster connectivity; grep-like search is optimized for per-job or per-experiment log review, so massive multi-cluster aggregation may face performance constraints.