fetch-logs

Fetch PT_Log files from Classic Mac test machines via FTP.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/matthewdeaves/peertalk --skill fetch-logs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fetch-logs
Source: https://github.com/matthewdeaves/peertalk/tree/main/.claude/skills/fetch-logs
Command: npx skills add https://github.com/matthewdeaves/peertalk --skill fetch-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classic Mac test runs generate PT_Log logs that are scattered across machines, making debugging and cross-machine comparison slow and error-prone. This Skill centralizes retrieval of PT_Log outputs from configured Macs via FTP, enabling faster troubleshooting and verification.

Core Features & Use Cases

  • Retrieve the latest or a specific PT_Log session from a single machine.
  • Fetch logs across multiple machines or entire platforms (MacTCP, Open Transport, AppleTalk) and compare results side-by-side when needed.
  • Save logs locally in a structured directory (logs/{machine}/session-<timestamp>.log) with a concise summary of log levels (INFO/WARN/ERROR).

Quick Start

Fetch the latest PT_Log from a Classic Mac test machine and save it locally for analysis.

Frequently Asked Questions about fetch-logs

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

FAQPage Schema
How do I fetch PT_Log files from Classic Mac test machines for debugging?▼

Fetch PT_Log files from Classic Mac test machines by retrieving them via FTP and saving the outputs locally in a structured logs directory. This centralizes the scattered logs to streamline troubleshooting of PeerTalk MCP server tests.

Can I compare PT_Log outputs from multiple Macs side-by-side?▼

Yes, you can compare PT_Log outputs side-by-side by fetching logs across an entire platform group or all configured Macs. The retrieval process supports optional side-by-side comparison to verify results across different machines.

Do I need an active MCP server to retrieve logs from Mac test machines?▼

Yes, retrieving PT_Logs from Mac test machines requires an active MCP server. You also need accessible PT_Log generation on the target machines, FTP access to those machines, and a local directory for storing the fetched logs.

How are fetched PT_Logs stored locally on my machine?▼

Fetched PT_Logs are stored locally in a structured directory using the format logs/{machine}/session-<timestamp>.log. Each retrieved log file is accompanied by a concise summary of its log levels, including INFO, WARN, and ERROR entries.

What is the best way to retrieve logs from different Classic Mac networking platforms?▼

The best way to retrieve logs from different Classic Mac networking platforms is to fetch PT_Logs by platform group, such as MacTCP, Open Transport, or AppleTalk. This allows you to gather logs from all machines within a specific platform category for analysis.

Why does fetching logs from Mac test machines fail without FTP access?▼

Fetching logs fails without FTP access because the retrieval mechanism relies on FTP to connect to the Classic Mac test machines and download the PT_Log outputs. Ensuring FTP access and active PT_Log generation on the targets is required for successful transfers.