get-job-logs

Fetch NovaDB job execution logs and save them to a local file.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/novadb/claude-plugins --skill get-job-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: get-job-logs
Source: https://github.com/novadb/claude-plugins/tree/main/consulting/skills/get-job-logs
Command: npx skills add https://github.com/novadb/claude-plugins --skill get-job-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve and persist execution logs for a specific NovaDB job so engineers and consultants can inspect runtime behavior, diagnose failures, and archive outputs without manually downloading streams.

Core Features & Use Cases

  • Fetch logs for a given jobId and write them to a local file path for inspection or archival.
  • Optional targetPath parameter controls the saved filename and location; parent directories are created automatically.
  • Enforces safety by rejecting absolute paths and path traversal, and provides a sensible default filename when targetPath is omitted.
  • Use cases include debugging failed jobs, preserving audit trails, and collecting logs for postmortem analysis.

Quick Start

Fetch the logs for job abc-123 and save them to logs/job-abc-123.txt.

Frequently Asked Questions about get-job-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save NovaDB job execution logs to disk for debugging?

To save NovaDB job logs to disk, provide a jobId to fetch the execution log streams and write them to a local file. An optional targetPath parameter controls the saved filename and location, automatically creating parent directories.

What is the best way to retrieve job logs for a failed NovaDB workflow?

Retrieving job logs for a failed NovaDB workflow requires passing the jobId to stream and persist the runtime output locally. This allows engineers to inspect runtime behavior, diagnose failures, and archive outputs without manual downloads.

Can I use an absolute path when saving job logs to a specific directory?

No, you cannot use an absolute path when saving job logs to a specific directory. The targetPath parameter enforces safety by rejecting absolute paths and path traversal, providing a sensible default filename when a valid targetPath is omitted.

Do I need a jobId to fetch logs from a NovaDB MCP job workflow?

Yes, a jobId parameter is required to fetch logs from a NovaDB MCP job workflow. This identifier retrieves the specific stored log streams that must be accessed via the novadb_cms_get_job_logs tool to write and save the file locally.