← Back to Skills Marketplace
191
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install server-log-analysis-en
Description
Connect to remote servers over SSH, read sibling config.yaml to understand service metadata and log locations, download only required log snippets to local t...
Usage Guidance
Before installing or running this skill: 1) Inspect config.yaml and remove any real credentials—do not keep plaintext passwords or private keys in the skill folder. Replace them with references to environment variables or an external secret manager. 2) Confirm that you explicitly consent to any SSH connections the skill will make and restrict connections to only authorized hosts. 3) Review the 'local_temp_dir' and ensure downloaded logs are stored in a controlled location, rotated, and deleted when no longer needed to avoid leaving sensitive data on the agent host. 4) Prefer SSH key-based auth and jump-host configuration rather than root/password; update config.yaml to use auth.method and auth.password_env or key references as suggested in reference.md. 5) If you need an audit trail, log when and what was downloaded and who authorized the operation. 6) If you cannot verify that config.yaml contains only placeholders, treat the bundle as potentially leaking secrets and do not use it until sanitized. If you want a safer setup, ask the skill author to remove credentials from the package and to declare the required environment variables (e.g., SSH_KEY, SSH_USER) in the skill metadata.
Capability Analysis
Type: OpenClaw Skill
Name: server-log-analysis-en
Version: 1.0.0
The skill bundle is designed for remote server log analysis via SSH but contains a significant security vulnerability in 'config.yaml', which includes hardcoded root credentials (username: root, password: password). While 'SKILL.md' and 'reference.md' provide instructions to minimize data collection and avoid storing plaintext secrets, the inclusion of default/weak credentials in the configuration file poses a high risk of unauthorized access and potential misuse of the SSH capabilities.
Capability Assessment
Purpose & Capability
The skill's behavior (connect over SSH, read a sibling config.yaml for connection info and log paths, download log snippets to local temp) aligns with the stated purpose. However, config.yaml includes an explicit 'connections' entry with a plaintext password (username: root, password: password) while the skill declares no required credentials or environment variables. That mismatch (embedded credentials in shipped config but no declared required secrets) is incoherent and risky.
Instruction Scope
SKILL.md narrowly defines a safe workflow (remote pre-checks, minimal downloads, do not modify remote files unless requested). It explicitly tells the agent to read local config.yaml and reference.md first, then perform SSH checks and fetch snippets to local temp. This stays within the expected scope, but the instructions allow downloading arbitrary log files (which can contain sensitive data) and say 'do not auto-delete downloaded logs' by default—this can create persistent copies of sensitive data if not managed. The guidance to prefer environment-managed credentials is present, but the shipped config contradicts that.
Install Mechanism
Instruction-only skill with no install spec or code files. That minimizes supply-chain risk since nothing is downloaded or executed by an installer.
Credentials
The skill requires SSH access to remote hosts to fulfill its purpose, but the registry metadata declares no required credentials or environment variables. The included config.yaml contains a 'connections' entry with plaintext credentials (host, username, password). Shipping sample (or placeholder) credentials is common, but presence of plaintext credentials in the skill bundle is a red flag: it either (a) encourages storing secrets in files, or (b) could contain real credentials accidentally. The skill does advise using env vars or key files, but does not enforce or declare that requirement.
Persistence & Privilege
The skill is not always-enabled, does not request system-wide changes, and does not modify other skills' configs. Autonomous invocation is allowed (platform default); combined with SSH capability this increases blast radius, but autonomy alone is expected and not flagged by itself.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install server-log-analysis-en - After installation, invoke the skill by name or use
/server-log-analysis-en - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial public release.
- Allows connecting to remote servers via SSH to analyze server logs.
- Reads service and log location data from a local config.yaml file.
- Downloads only necessary log snippets to a local temp directory for analysis.
- Follows clear steps: read config, scope investigation, check logs remotely, fetch logs, analyze, and report conclusions.
- Includes structured troubleshooting and security guidelines.
- English documentation rewritten for clarity and accessibility.
Metadata
Frequently Asked Questions
What is server-log-analysis-en?
Connect to remote servers over SSH, read sibling config.yaml to understand service metadata and log locations, download only required log snippets to local t... It is an AI Agent Skill for Claude Code / OpenClaw, with 191 downloads so far.
How do I install server-log-analysis-en?
Run "/install server-log-analysis-en" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is server-log-analysis-en free?
Yes, server-log-analysis-en is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does server-log-analysis-en support?
server-log-analysis-en is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created server-log-analysis-en?
It is built and maintained by hgvgfgvh (@hgvgfgvh); the current version is v1.0.0.
More Skills