capture-wsl-systemctl

Capture WSL systemctl diagnostics via SSH and write timestamped logs.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/doesitscript/dotfile-vnext --skill capture-wsl-systemctl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-wsl-systemctl
Source: https://github.com/doesitscript/dotfile-vnext/tree/main/.cursor/skills/capture-wsl-systemctl
Command: npx skills add https://github.com/doesitscript/dotfile-vnext --skill capture-wsl-systemctl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps teams quickly collect diagnostic output from a WSL Ubuntu distro via SSH, producing timestamped logs for troubleshooting.

Core Features & Use Cases

  • WSL diagnostics on demand: captures systemctl status, unit lists, and journal logs to a central log folder for analysis.
  • Timestamped archival: stores logs under logs/wsl-systemctl with a deterministic filename for traceability.
  • Flexible target selection: defaults to server-225-wsl but can use a user-specified host.

Quick Start

Run the capture-wsl-systemctl skill to collect WSL diagnostics from the connected WSL host.

Frequently Asked Questions about capture-wsl-systemctl

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

FAQPage Schema
How do I capture WSL systemctl logs with timestamps for troubleshooting?

You can capture WSL systemctl logs with timestamps by running this Skill, which connects to a WSL host via SSH, collects service status and journal entries, and saves the diagnostic output to a timestamped file under logs/wsl-systemctl for traceability.

What systemctl diagnostics can I collect from a remote WSL host?

From a remote WSL host, you can collect systemctl diagnostics including service status, unit lists, failure states, and recent journal entries. This Skill retrieves this data via SSH and writes it to a timestamped log file.

Do I need SSH access to run WSL systemctl diagnostics?

Yes, you need SSH access to run WSL systemctl diagnostics using this Skill. It connects to a WSL host, defaulting to server-225-wsl, to retrieve and record service status and journal logs.

Can I specify a different WSL host when collecting systemctl logs?

Yes, you can specify a different WSL host when collecting systemctl logs. While the Skill defaults to server-225-wsl, it supports flexible target selection so you can direct the SSH connection to any user-specified host.

Where are WSL systemctl diagnostic logs saved?

WSL systemctl diagnostic logs are saved under the logs/wsl-systemctl directory. The Skill writes the captured status, unit lists, and journal entries to a file with a deterministic, timestamped filename for reliable archival and traceability.