home / skills / trpc-group / trpc-agent-go / envdump

envdump skill

safe

/openclaw/skills/envdump

This skill dumps basic system and environment information to out/env.txt to aid debugging and auditing.

npx playbooks add skill trpc-group/trpc-agent-go --skill envdump

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

305 B

---
name: envdump
description: Dump basic environment info to out/env.txt.
metadata:
  { "openclaw": { "requires": { "bins": ["bash"] } } }
---

Overview

This skill collects basic system/environment info and writes it to `out/`.

Command

bash scripts/envdump.sh out/env.txt

Output Files

- out/env.txt

Overview

This skill collects basic system and runtime environment information and writes it to out/env.txt. It is designed as a lightweight diagnostic tool to capture OS, shell, path, and common tool versions. Run it before debugging or packaging to get a reproducible snapshot of the environment. The output is a single plain-text file suitable for sharing or attaching to issue reports.

How this skill works

The skill executes a small shell script that probes common environment data points and redirects the consolidated output into out/env.txt. It gathers details such as kernel/version info, shell identity, PATH, locale, Go version, and presence/version of common tools. The script is idempotent and overwrites the destination file each run to ensure the snapshot is current. No external network access is required; it only reads local system state and writes the text file.

When to use it

Before opening a bug report to provide reproducible environment details.
When onboarding a new developer to capture their baseline machine state.
Prior to running CI or agent workflows to document runner configuration.
When diagnosing toolchain or dependency issues that may be environment-dependent.
As part of a packaging or release checklist to record build environment.

Best practices

Run the script from the repository root so out/ paths are consistent.
Commit or attach out/env.txt only when it contains non-sensitive data; review for secrets first.
Use the latest script version to capture any newly added probes (e.g., extra tool checks).
Include the env dump alongside logs and test output to give full context for debugging.
Automate env dumps in CI jobs when debugging intermittent environment-specific failures.

Example use cases

A developer attaches out/env.txt to an issue to show OS, Go version, and PATH differences.
A CI failure investigator compares env dumps from passing and failing runs to find discrepancies.
A new team member shares their env dump so maintainers can reproduce a local problem.
A release engineer archives env dumps for reproducibility of a build artifact.
An ops engineer collects env snapshots across hosts when onboarding a new deployment.

FAQ

What exactly does the script record?

It captures core environment details such as OS release, kernel, shell, PATH, locale, Go toolchain version, and availability of common developer tools.

Is any sensitive information recorded?

The script targets general system metadata, but PATH or environment variables might reveal usernames or custom paths; review the file before sharing publicly.