worker

Diagnoses worker service failures, job queue stalls, and git sync issues on a VPS.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/NicolaeRotaru/ad-mycity --skill worker-nicolaerotaru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/NicolaeRotaru/ad-mycity/tree/main/.claude/skills/worker
Command: npx skills add https://github.com/NicolaeRotaru/ad-mycity --skill worker-nicolaerotaru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the worker — the component that actually executes jobs for the MyCity marketplace — stops, crashes, silently drops jobs, or fails to publish memory, this Skill provides a structured deep-diagnosis procedure to find the true root cause instead of guessing from surface symptoms. ## Core Features & Use Cases - Eleven-dimension inspection: Covers systemd services and timers, job queue age analysis, atomic job claiming, orphaned job recovery, file locks, git alignment, pause kill-switch behavior, AI engine quota/credentials, disk and memory health, and the VPS self-report bridge. - Evidence-based diagnosis: Distinguishes what can be proven from the VPS versus what can only be inferred remotely from Supabase queue traces and git commit cadence, marking every finding as proven, broken, or not observable. - Structured outputs: Writes defects with root cause and behavioral verification tests into the repair backlog, produces an impact-ordered audit report, and prepares exact paste-ready commands for actions only the human owner can perform. - Use Case: The chat stops responding and the dashboard shows stale data. Use this Skill to trace whether the cause is a crashed service, a stuck in-progress job, an expired AI session, or unpublished VPS commits. ## Quick Start Use the worker skill to diagnose why the worker has stopped picking up jobs from the queue and produce a root-cause report.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I diagnose why a systemd worker service keeps crashing?▼

Check systemctl is-active for the service, then read the NRestarts property with systemctl show — a restart count above 20 means it crash-loops rather than runs. Inspect the last 60 journalctl lines to find the actual failure cause.

How to detect stuck jobs in a Supabase job queue?▼

Look at job age rather than count: pending jobs older than about 15 minutes indicate claiming is broken or the worker is stopped, while in-progress jobs older than 45 minutes mean a worker died mid-job and left it hanging.

Why does a worker service show active but still not work?▼

A service that restarts every 40 seconds appears active at every check. Other causes include an expired AI session, an active pause kill-switch, or a leftover lock file from a dead process silently blocking all runs.

Can worker diagnosis be done remotely without VPS access?▼

Yes, but only by traces: queue state and heartbeat on Supabase, the published health report in git, and commit cadence from the VPS. Service-level claims remain unverifiable and must be marked as not observable.

What are the limits of this worker diagnosis approach?▼

It never restarts services, edits environment files, deploys, or clears the queue — those remain manual owner actions. It also does not cover quick health checks or actual repair, which belong to separate skills.