job-review

Evaluating project manager effectiveness involves parsing job stores like .claude/data.json, inspecting recent git commits, and testing scripts to surface gaps and improvement opportunities. The process classifies findings across five dimensions and records actionable outcomes to job notes.

Job orchestration health assessment scores Job Quality, Evidence Chain, Growth Rate, Compute Distribution, and Context Hygiene to detect stale contexts or missing job steps. You need it for periodic maintenance, post-job audits, or explicit review requests to ensure system reliability.

Yes, you need jq installed as a dependency to review PM effectiveness and orchestration health. The skill uses jq to parse structured data from .claude/data.json and extract job metrics required for the five-dimension evaluation.

Scheduling periodic reviews applies scheduled review triggers to repository job stores and git histories, classifying evaluation dimensions to identify stale focused jobs or PM phase and order problems, then generating maintenance jobs to address them.

Automating post-job audits requires applying review triggers to parse .claude/data.json and inspect commits and scripts, classifying five evaluation dimensions to surface missing job steps or resources, and emitting structured findings to improvement backlogs.

RED outcomes for Context Hygiene and Compute Distribution indicate stale focused contexts or imbalanced compute allocation detected during the five-dimension evaluation. The skill inspects git histories and script outputs to classify these issues and suggests fixes for PM skills and jobs.