jobs

Track active and completed simulation jobs in a centralized JOBS.md file.

1|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/BioKT/Skills-BIOKT --skill jobs-biokt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jobs
Source: https://github.com/BioKT/Skills-BIOKT/tree/main/jobs
Command: npx skills add https://github.com/BioKT/Skills-BIOKT --skill jobs-biokt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain a JOBS.md file to track active and completed simulation jobs across all machines, keeping teams synchronized on work progress.

Core Features & Use Cases

  • Show current JOBS.md (create if absent)
  • Add new job rows with /jobs add
  • Update statuses across hosts/SLURM with /jobs update
  • Archive completed jobs to a Completed section with /jobs clean

Quick Start

Create a JOBS.md in the project root and run /jobs to view it or /jobs add to log new jobs.

Frequently Asked Questions about jobs

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

FAQPage Schema
How do I track and monitor simulation jobs across multiple machines?

You can track simulation jobs across machines by maintaining a centralized JOBS.md file that logs job statuses, keeping teams synchronized on work progress across local clusters and SLURM environments.

What is the best way to log HPC and computational simulation statuses in a shared project?

Logging HPC simulation statuses is done by adding job rows to a centralized JOBS.md file, which acts as a shared ledger to monitor active and completed work across all project environments.

How do I add and update SLURM job records for my project?

You can add new SLURM job records using the add command and update their current statuses across hosts using the update command, writing all changes directly into the project's JOBS.md file.

Do I need a specific file format to start tracking jobs in my project root?

Yes, you need a JOBS.md file located in the project root to start tracking jobs. If the file is absent, the tracking workflow can automatically create it when you view or add a job.

How do I clean up and archive completed simulation jobs in my tracking log?

To clean up completed simulation jobs, use the clean command to move finished rows into a Completed section within the JOBS.md, applying strike-through formatting to clearly separate active work.

Can I use this job tracking workflow for local clusters without a workload manager?

Yes, this simulation job tracking workflow supports various environments including local clusters, allowing you to manually log and monitor statuses even without an automated workload manager like SLURM.