loki-query
v1.0.1Query Loki logs by traceid, keywords, pod, namespace, labels, or time range to debug and analyze Kubernetes application issues via API.
⭐ 1· 74·0 current·0 all-time
byGoodAtMe@peintune
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Loki queries by traceid/labels/time/pod/namespace) align with the included CLI script and examples. The skill only requires a Loki API URL and a LogQL query; nothing requested is disproportionate to log querying.
Instruction Scope
SKILL.md instructs running the bundled Python script or using kubectl port-forward/curl to reach Loki. The instructions do not ask the agent to read unrelated files or environment variables. Note: examples include kubectl exec/port-forward which legitimately require cluster access — expected for this use case.
Install Mechanism
No install spec (instruction-only) and a small included Python script. Nothing is downloaded or written to disk automatically by an installer, so installation risk is minimal.
Credentials
The skill declares no required environment variables or credentials. The script accepts a loki URL but does not attempt to read secrets from the environment. If the target Loki requires authentication, the skill currently has no explicit mechanism to provide auth headers (caller would need to run an authenticated proxy or modify the script).
Persistence & Privilege
always is false and the skill does not request persistent presence or modify other skills or system settings. Autonomous invocation is allowed by default but is not combined with other concerning privileges.
Assessment
This skill appears coherent for querying Loki. Before installing, consider: (1) ensure you trust the Loki endpoint you point it at (the script will send queries to whatever loki-url you provide); (2) if your Loki requires authentication, this script does not have built-in auth support — you would need to provide a secure proxy or extend the script rather than handing credentials to an unknown skill; (3) the examples use kubectl port-forward/exec which require cluster access — only run those commands in clusters you control; (4) as always, review the included script locally before running it in sensitive environments.Like a lobster shell, security has layers — review code before you run it.
latestvk97e6sbw9dthzar8mz7rtyadz983x3r7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.