Agent skill

Worker

by HazAT in HazAT/pi-config

Implement one todo or review-fix task supplied by a coordinator, verify it, create one focused commit, and report evidence through the current Superconductor session.

MITAuto-check passedDevelopment

Install Worker

skills CLI
$ npx skills add HazAT/pi-config --skill worker -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HazAT/pi-config worker --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/worker .claude/skills/worker && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
worker
GitHub stars
451
Token cost
~679 tokens
SKILL.md length
319 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Implement one todo or review-fix task supplied by a coordinator, verify it, create one focused commit, and report evidence through the current Superconductor session.

  • Works in 5 steps: Read and follow… → Review the complete diff and stage only… → Create exactly one focused commit; do… → …
  • Launched by /execute
  • SKILL.md covers Inputs, Implement and Verify, Commit and Final Report
  • Calls git

What it does

Worker is an agent skill from HazAT/pi-config. Implement one todo or review-fix task supplied by a coordinator, verify it, create one focused commit, and report evidence through the current Superconductor session. Use when launched by /execute, launched from a review repair loop, or asked to implement one assigned task.

Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Git. The repository describes itself as: My personal pi coding agent configuration - skills and extensions. The licence is MIT.

When your agent uses it

  • Launched by /execute
  • Launched from a review repair loop
  • Asked to implement one assigned task

Example prompts

  • “/worker”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read and follow ~/.pi/agent/skills/commit/SKILL.md.
  2. Review the complete diff and stage only this task's files.
  3. Create exactly one focused commit; do not push.
  4. Verify it with git show --stat --oneline HEAD and capture the full SHA.
  5. Confirm git status --short contains no uncommitted changes owned by this task.

What it can do on your machine

Read from SKILL.md and the folder at commit 655acd4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Worker loads about 679 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 319 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~679

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HazAT/pi-config at commit 655acd4, republished under its MIT licence (© HazAT). 319 words, ~679 tokens.

Download SKILL.mdSave it as .claude/skills/worker/SKILL.md (or your agent's skills folder).
name
worker
description
Implement one todo or review-fix task supplied by a coordinator, verify it, create one focused commit, and report evidence through the current Superconductor session. Use when launched by /execute, launched from a review repair loop, or asked to implement one assigned task.

Worker

Implement exactly the assigned todo or review-fix task. Do not redesign the plan, expand scope, launch agents, push, or edit coordinator handover files.

Inputs

The launch prompt must provide:

  • available absolute plan, todos, and review paths;
  • one task ID and its exact scope;
  • the checkout to use;
  • any additional acceptance constraints.

Read the supplied handover files directly and treat them as read-only. Inspect repository instructions, git status --short, and every target file before editing. If context is missing or unrelated dirty changes make an isolated commit unsafe, stop and report a blocker rather than guessing.

Implement and Verify

Keep changes limited to the assigned task and preserve unrelated work. Run the smallest meaningful tests, typecheck, build, or smoke checks required by its acceptance criteria. Remove temporary/debugging artifacts.

Run every mutation-capable verification command before the commit. After the final verification, inspect git status --short: include legitimate generated source changes in scope, or restore disposable generated output before reporting. If a post-commit hook or required check changes tracked files, reconcile those files, rerun the affected verification, and amend or create the requested single focused commit. Never report completion with task-owned changes left dirty.

If verification fails, do not commit partial work. Report the command, failure, and blocker.

Commit

After verification passes:

  1. Read and follow ~/.pi/agent/skills/commit/SKILL.md.
  2. Review the complete diff and stage only this task's files.
  3. Create exactly one focused commit; do not push.
  4. Verify it with git show --stat --oneline HEAD and capture the full SHA.
  5. Confirm git status --short contains no uncommitted changes owned by this task.

A no-op task may omit a commit only when the evidence proves no source change was needed.

Final Report

Return a concise final response for the coordinator to collect with sc agent read:

markdown
Status: DONE | BLOCKED
Task: TODO-NNN | REVIEW-FIX-NNN
Summary: ...
Files changed:
- `path` — ...
Verification:
- `command` — pass/fail and key output
Commit: `<full SHA> <subject>` | none
Risks: none | ...

The coordinator—not the worker—updates todo or review state. A terminal response is the handoff; do not write result artifacts or any other state file.

© HazAT, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/worker of HazAT/pi-config.

Open the folder on GitHubat commit 655acd4

Compare with similar skills

Worker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Worker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Worker this skillHazAT/pi-config451—~679Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything86k1 repos~1.2kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Codebase Knowledge Graph Q&A

    Egonex-AI/Understand-Anything

    Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.

    86k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Understand Explain

    Egonex-AI/Understand-Anything

    Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.

    86k GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed

More from HazAT/pi-config

All 10 skills in this repo
  • Session Reader

    HazAT/pi-config

    Efficiently read and analyze pi agent session JSONL files. An agent skill from HazAT/pi-config.

    451 GitHub stars~808 tokensUpdated 1 mo ago
    Auto-check passed
  • Defines the local standard for standalone Pi extension repositories.

    451 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Superconductor

    HazAT/pi-config

    Operates the super.engineering/Superconductor sc CLI for app-managed agents, teams, sessions, layouts, worktrees, and review threads.

    451 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Plan

    HazAT/pi-config

    Interactively investigate a request, compare approaches, and write the selected implementation plan to a supplied Markdown path.

    451 GitHub stars~528 tokensUpdated 1 mo ago
    Auto-check passed
  • Review

    HazAT/pi-config

    Coordinate a model-diverse local code review, automatically repair actionable findings with sequential workers, and re-review to a final verdict.

    451 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Configures a repository for super.engineering with repo-owned worktree setup and development-server scripts.

    451 GitHub stars~999 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Worker

What does Worker do?

Implement one todo or review-fix task supplied by a coordinator, verify it, create one focused commit, and report evidence through the current Superconductor session. Worker is an agent skill from HazAT/pi-config. Implement one todo or review-fix task supplied by a coordinator, verify it, create one focused commit, and report evidence through the current Superconductor session.

When should I use Worker?

Worker fits situations like: launched by /execute; launched from a review repair loop; asked to implement one assigned task.

How do I install Worker in Claude Code?

Run `npx skills add HazAT/pi-config --skill worker -a claude-code`. Or copy the skill folder (skills/worker in HazAT/pi-config) into .claude/skills/worker in your project. Claude Code loads it when a task matches its description.

How do I install Worker in Codex?

Run `npx skills add HazAT/pi-config --skill worker -a codex`. Or copy the skill folder (skills/worker in HazAT/pi-config) into .agents/skills/worker in your project. Codex loads it when a task matches its description.

Can I use Worker in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HazAT/pi-config --skill worker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/worker, .gemini/skills/worker, .github/skills/worker and .opencode/skills/worker in your project.

What does Worker need to run?

Going by SKILL.md and its folder, Worker needs the command-line tools its instructions call (git).

Does Worker access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Worker safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Worker use?

Worker is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Worker use?

About 679 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Worker?

Skills that share tags, products or a category with Worker: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Worker?

HazAT (a GitHub user) maintains it in HazAT/pi-config, which has 451 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on August 25, 2026.

Source: HazAT/pi-config on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.