Log Viewer

VerifiedCaution

Tail and search logs across trading platform services. Supports filtering by service, error level, regex search, time range, and live follow. Useful for debugging, monitoring, and quickly identifying issues in real-time.

Sby Skills Guide Bot
DevOpsIntermediate
6/2/2026
Claude Code
#logs#debugging#monitoring#kubernetes#docker

Recommended for

Automated summary

Tails and searches logs across trading platform services, supporting Docker Compose and Kubernetes environments.

Strengths

  • Advanced filtering by service, log level, regex pattern, and error-only mode.
  • Live follow mode (--follow) for continuous log streaming.
  • Error summary with counts and most recent messages.
  • Context lines around matches for search results.

Limitations

  • Requires services to be deployed with Docker Compose or Kubernetes.
  • Recognized log patterns are specific to a trading platform.
  • Advanced features (stern, kubectl) depend on target infrastructure.
When to use it

Use this skill to debug or monitor logs of an application in development or staging environments.

When not to use it

Do not use it for production logs that require a centralized log management solution (ELK, Splunk).

Security analysis

Caution
Quality score85/100

The skill is designed to access and filter logs via legitimate tools (docker, kubectl, stern). It does not instruct destructive actions, but the use of powerful shell commands with potentially unsanitized user input presents a moderate risk. The skill is inherently meant for debugging, but caution is warranted.

Findings
  • •Uses docker and kubectl commands with user-supplied arguments, which could allow command injection if the agent does not sanitize inputs (e.g., service name with shell metacharacters).
  • •Log output may contain sensitive information (API keys, tokens, PII) depending on the logging practices of the services.
How this analysis is made

Examples

Tail all service logs
Show me the last 50 lines of logs from all services.
Search for failure patterns
Search logs for 'order.*failed' and show matches with context lines.
Show only errors
Show me only error logs from the last 30 minutes across all services.

name: logs description: Tail and search service logs with filtering argument-hint: "[service|--search pattern|--errors]"

Log Viewer

Tail and search logs across trading platform services.

Usage

  • /logs - Tail all services (last 100 lines)
  • /logs api - Tail specific service
  • /logs --errors - Show only errors across all services
  • /logs --search "order.*failed" - Search with regex
  • /logs api --since 1h - Logs from last hour
  • /logs --level error - Filter by log level
  • /logs executor --follow - Live tail (follow mode)

Services

| Service | Container | Log Path | |---------|-----------|----------| | api | trading-api | stdout | | ui | trading-ui | stdout | | executor | trading-executor | stdout | | risk | trading-risk | stdout | | worker | trading-worker | stdout | | ml-server | ml-server | stdout | | market-ingest | market-ingest | stdout | | backtester | backtester | stdout |

Instructions

When this skill is invoked:

  1. Parse arguments:

    • Service name: Filter to specific service
    • --errors: Filter level=error or level=ERROR
    • --search <pattern>: Grep with regex pattern
    • --since <duration>: Time filter (1h, 30m, 1d)
    • --level <level>: Filter by log level
    • --follow / -f: Live tail mode
    • --lines N / -n N: Number of lines (default 100)
  2. For Docker Compose (dev):

    # Single service
    docker compose logs $SERVICE --tail $LINES $FOLLOW_FLAG
    
    # All services with grep
    docker compose logs --tail $LINES | grep -E "$PATTERN"
    
    # Errors only
    docker compose logs --tail 500 | grep -iE "error|exception|failed|traceback"
    
  3. For Kubernetes (staging/prod):

    # Single pod
    kubectl logs -l app=$SERVICE -n trading --tail=$LINES $FOLLOW_FLAG
    
    # With stern for multi-pod
    stern $SERVICE -n trading --since $SINCE
    
  4. Display formatted output:

    [09:31:05] api       INFO   Request: POST /orders
    [09:31:05] executor  INFO   Order received: abc123
    [09:31:06] executor  ERROR  Order failed: insufficient margin
    [09:31:06] risk      WARN   Margin utilization at 95%
    
  5. For --errors, highlight and summarize:

    ERROR SUMMARY (last 1h)
    ─────────────────────────────────────────────────────────
    executor    12 errors   "insufficient margin" (8), "timeout" (4)
    api         3 errors    "validation failed" (3)
    ml-server   1 error     "model not found" (1)
    
    Most recent errors:
    [09:31:06] executor  Order failed: insufficient margin for AAPL x100
    [09:30:45] executor  Connection timeout to broker
    
  6. For --search, show matches with context:

    • 2 lines before and after each match
    • Highlight matching text
    • Show total match count
  7. Common log patterns to recognize:

    • Order lifecycle: submitted → acknowledged → filled/rejected
    • Errors: exceptions, tracebacks, failed operations
    • Performance: slow queries, timeouts
    • Security: auth failures, rate limits

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/log-viewer-mmbizkh8/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/log-viewer-mmbizkh8' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/log-viewer-mmbizkh8/download' --output '.skill-downloads/log-viewer-mmbizkh8/SKILL.md.part' && mv '.skill-downloads/log-viewer-mmbizkh8/SKILL.md.part' '.skill-downloads/log-viewer-mmbizkh8/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/log-viewer-mmbizkh8/SKILL.md' && test -s '.skill-downloads/log-viewer-mmbizkh8/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/logs' && cp -R '.skill-downloads/log-viewer-mmbizkh8' '.claude/skills/logs'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/log-viewer-mmbizkh8'

openskills read 'log-viewer-mmbizkh8'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/log-viewer-mmbizkh8/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills