Log Aggregation

Centralize, parse, search, and analyze logs from multiple sources with real-time alerts and visualizations for debugging and monitoring.

Security Scan

The skill's requested actions (collecting and analyzing logs) align with its name and description, but the instructions are vague about sources and credentials and could enable access to sensitive logs if the agent is given broad system or cloud access.

Purpose & Capability

Name, description, and features (collection, parsing, search, alerting, visualization) are coherent. Requesting Node.js 18+ as an implementation requirement (not enforced) is reasonable for a log-related tool; no unrelated credentials, binaries, or paths are demanded up-front.

Instruction Scope

SKILL.md explicitly instructs collecting logs from files (/var/log/app/*.log), stdout, syslog, and cloud services — actions that are consistent with log aggregation but are broad. Instructions are example-like and vague about which cloud services, endpoints, or credentials to use; that vagueness gives the agent wide discretion and could result in reading or transmitting sensitive logs unless constrained by the runtime environment and policies.

Install Mechanism

No install spec and no code files — lowest-risk distribution model. Nothing is downloaded or written by the skill itself.

Credentials

The skill does not request environment variables, credentials, or config paths in the metadata. However, the SKILL.md mentions optional cloud storage backends (Elasticsearch, Loki) without describing required credentials; integrating those would require external credentials which are not declared here.

Persistence & Privilege

always:false and user-invocable:true — normal and appropriate. The skill does not request persistent elevation or modify other skills' configs.

Assessment

This skill is broadly consistent with a log-aggregation tool, but it's instruction-only and vague about which sources and cloud services to use. Before installing: (1) confirm how your agent runtime enforces access controls — ensure it cannot read system logs or cloud accounts you don't want exposed; (2) plan credentials for Elasticsearch/Loki (if used) and supply them securely rather than letting the agent request them ad hoc; (3) test in a restricted environment (non-production) to observe what files/endpoints the agent actually accesses; (4) apply least-privilege permissions for any log sources and audit log exports to prevent accidental exposure of sensitive information.

Centralized log collection and analysis for AI agents. Aggregate logs from multiple sources, search, and generate insights.

Overview

A comprehensive log management system that helps agents collect, parse, search, and analyze logs from various sources.

Features

• Log Collection: Gather logs from files, stdout, syslog, cloud services
• Parsing: Automatic log parsing and field extraction
• Search: Powerful full-text search and filtering
• Aggregation: Group and summarize log data
• Alerting: Detect errors and anomalies in real-time
• Visualization: Log dashboards and charts
• Export: Export logs to files, SIEM systems

Commands

Collect Logs

collect logs from /var/log/app/*.log

Search Logs

search error logs from last hour

Create Alert

alert when error rate exceeds 10 per minute

Use Cases

• Application debugging
• Error tracking
• Security audit
• Performance analysis
• Compliance logging

Requirements

• Node.js 18+
• Optional: Elasticsearch, Loki for storage