update-job

Update NovaDB job state and retention settings via the novadb_cms_update_job tool.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable operators to change a NovaDB job's lifecycle signals and retention window without manual API calls, streamlining routine job control and audit logging.

Core Features & Use Cases

  • State Control: Request job termination or restart by setting state to the allowed values (4 = KillRequested, 5 = RestartRequested).
  • Retention Management: Extend or shorten the job retention period via an ISO-8601 retainUntil timestamp.
  • Audit Metadata: Optionally include an acting username for traceable updates.
  • Use Case: An operator can request a running job to be killed or restarted after investigating failures, or extend retention for a job pending troubleshooting.

Quick Start

Update job abc-123 to request a kill by setting state to 4 and include your username for auditing.

Frequently Asked Questions about update-job

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

FAQPage Schema
How do I request a kill or restart for a NovaDB job?

To request a kill or restart for a NovaDB job, you update the job state using the update-job skill. You must provide the jobId and set the state parameter to 4 for KillRequested or 5 for RestartRequested, which then invokes the novadb_cms_update_job tool.

How can I change the retention period for a NovaDB job?

You can change the retention period for a NovaDB job by providing an ISO-8601 timestamp to the retainUntil parameter. This adjusts the job's retention window directly through the novadb_cms_update_job tool without manual API calls.

Can I include audit metadata when updating NovaDB job states?

Yes, you can include audit metadata when updating NovaDB job states by providing an optional username parameter. This allows operators to trace who requested the kill, restart, or retention adjustments for troubleshooting and audit logging.

What state values are supported when updating NovaDB job lifecycle signals?

When updating NovaDB job lifecycle signals, the state parameter is limited to values 4 and 5. Value 4 corresponds to KillRequested and value 5 corresponds to RestartRequested, ensuring controlled state transitions.

Does updating NovaDB job retention require manual API configuration?

Updating NovaDB job retention does not require manual API configuration. The update-job skill streamlines routine job control by accepting a jobId and an ISO-8601 retainUntil timestamp to automatically invoke the novadb_cms_update_job tool.

What do I need to provide to update a NovaDB job via MCP?

To update a NovaDB job via MCP, you need the specific jobId and optionally the state (4 or 5), an ISO-8601 retainUntil timestamp, and a username. The skill returns the updated job object after processing the request.