worker

Execute assigned tasks with context validation and local commits.

3|4|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/nicsuzor/academicOps --skill worker-nicsuzor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/nicsuzor/academicOps/tree/main/.agent/skills/worker
Command: npx skills add https://github.com/nicsuzor/academicOps --skill worker-nicsuzor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the execution of pre-defined tasks, ensuring they are completed accurately and efficiently within specified boundaries.

Core Features & Use Cases

  • Task Execution: Runs assigned tasks based on a provided workflow and context.
  • Scope Adherence: Strictly operates within defined file and modification boundaries.
  • Progress Tracking: Updates task status and reports completion or failure.
  • Use Case: An agent receives a task to update documentation in a specific directory. The worker Skill executes the editing, commits the changes locally, and reports success or failure based on predefined criteria.

Quick Start

Execute the task described in the provided context file.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I automate task execution for an autonomous agent within strict scope boundaries?

Autonomous task execution is handled by an agent that validates injected context, claims the task, plans work via TodoWrite, executes steps, and commits locally. It strictly adheres to defined file and modification boundaries, failing fast on any ambiguity.

What is the best way to ensure an autonomous agent commits code locally after completing a task?

To ensure an autonomous agent commits code locally after task completion, the workflow includes built-in quality gates that verify work against predefined criteria before performing a local commit and reporting final status.

How does scope adherence work when an agent receives context for task management?

Scope adherence works by validating the input context upon task reception, ensuring the agent only operates within defined file and modification boundaries, and immediately failing if the context is ambiguous or out of scope.

Can I use TodoWrite to plan work steps for automated workflow execution?

Yes, TodoWrite is used to plan work steps during automated workflow execution. After claiming a task with full context injection, the agent uses TodoWrite to sequence the execution steps before applying quality gates and committing locally.

Why does an autonomous task executor fail fast on ambiguity during code commit workflows?

An autonomous task executor fails fast on ambiguity to maintain strict scope adherence and prevent unintended modifications. If the injected context is unclear, it halts execution immediately rather than risking out-of-bound changes during the code commit process.

What are the limitations of using a worker agent for task management?

The primary limitation is its rigid scope boundary enforcement; the agent cannot perform modifications outside its explicitly defined context. Additionally, it requires full context injection to operate and will halt execution if it encounters ambiguous instructions.