Skill

begin-coding-worker

Start an adaptive coding loop that dynamically adjusts interval based on activity — short intervals when busy, longer when idle.

Install

npx claudepluginhub vm0-ai/team-skills --plugin coding-team

Tool Access

This skill uses the workspace's default tool permissions.

Preview

1. Determine the worker label and run the coding worker script, capturing stdout:

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

159.9k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

159.9k

next-compile

1 file

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

vercel-next-js-2

139.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 4, 2026

Actions

View Source View Plugin View on GitHub View README

Determine the worker label and run the coding worker script, capturing stdout:

PROJECT_ROOT=$(git rev-parse --show-toplevel)
_LABEL="${ARGUMENTS:-$("$PROJECT_ROOT/scripts/cn.sh")}"
${CLAUDE_PLUGIN_ROOT}/scripts/coding-worker.sh "$_LABEL"

Parse the first line INTERVAL:N and save N.
Use CronList to check if a recurring cron job for /begin-coding-worker already exists.
- If a matching job exists and its interval differs from N minutes, delete it with CronDelete and create a new recurring cron with */N * * * * and prompt /begin-coding-worker $ARGUMENTS.
- If a matching job exists and its interval already matches N minutes, do nothing (keep it as-is).
- If no matching job exists, create a new recurring cron with */N * * * * and prompt /begin-coding-worker $ARGUMENTS.
If the remaining output (after the first line) is "idle", stop here — the recurring cron will trigger the next check.
If the remaining output is NOT "idle", launch a general-purpose Agent (subagent) with that output as the prompt. Do NOT execute the instructions yourself — always delegate to a subagent. Wait for the subagent to complete before returning.