Issue Progress Tracking
yonatangross/orchestkit
GitHub issue workflow ceremony using gh CLI — labels issues as in-progress, creates feature branches (issue/N-description), commits with issue references, posts progress comments, and links PRs with…
Issue-led atomic work logging. An agent skill from tokenbender/agent-guides.
Install Worklog
$ npx skills add tokenbender/agent-guides --skill worklog -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tokenbender/agent-guides worklog --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tokenbender/agent-guides.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-skills/worklog .claude/skills/worklog && rm -rf skills-srcUse ~/.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/
Install the "worklog" agent skill from https://github.com/tokenbender/agent-guides/tree/main/claude-skills/worklog into .claude/skills/worklog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worklog", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tokenbender/agent-guides/tree/main/claude-skills/worklogType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tokenbender/agent-guides --skill worklog -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tokenbender/agent-guides worklog --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tokenbender/agent-guides.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-skills/worklog .agents/skills/worklog && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "worklog" agent skill from https://github.com/tokenbender/agent-guides/tree/main/claude-skills/worklog into .agents/skills/worklog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worklog", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tokenbender/agent-guides --skill worklog -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tokenbender/agent-guides worklog --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tokenbender/agent-guides.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-skills/worklog .cursor/skills/worklog && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "worklog" agent skill from https://github.com/tokenbender/agent-guides/tree/main/claude-skills/worklog into .cursor/skills/worklog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worklog", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tokenbender/agent-guides.git --path claude-skills/worklog--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tokenbender/agent-guides --skill worklog -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tokenbender/agent-guides worklog --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tokenbender/agent-guides.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-skills/worklog .gemini/skills/worklog && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "worklog" agent skill from https://github.com/tokenbender/agent-guides/tree/main/claude-skills/worklog into .gemini/skills/worklog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worklog", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tokenbender/agent-guides worklogInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tokenbender/agent-guides --skill worklog -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tokenbender/agent-guides.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-skills/worklog .github/skills/worklog && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "worklog" agent skill from https://github.com/tokenbender/agent-guides/tree/main/claude-skills/worklog into .github/skills/worklog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worklog", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tokenbender/agent-guides --skill worklog -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tokenbender/agent-guides worklog --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tokenbender/agent-guides.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-skills/worklog .opencode/skills/worklog && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "worklog" agent skill from https://github.com/tokenbender/agent-guides/tree/main/claude-skills/worklog into .opencode/skills/worklog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worklog", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
worklog- GitHub stars
- 367
- Token cost
- ~1.6k tokens
- SKILL.md length
- 692 words
- Files
- 2
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Issue-led atomic work logging. An agent skill from tokenbender/agent-guides.
- Works in 5 steps: Inspect existing issues before creating… → Reuse an existing master issue if it… → Create a new master issue when no… → …
- The user says worklog
- SKILL.md covers Core Contract, Before Touching GitHub, Starting A Worklog and During Work, plus 4 more sections
- Calls git and gh
What it does
Worklog is an agent skill from tokenbender/agent-guides. Issue-led atomic work logging. Use whenever the user says "worklog" or asks to run, apply, start, maintain, update, summarize, or close a worklog; also use for issue-led development, master or umbrella issue tracking, one-issue-per-bug/feature/change workflows, atomic issue-scoped commits, GitHub issue comment journals, closeout summaries, durable engineering ledgers, and making sure no compatibility, migration, cleanup, or residual-risk work is left hanging without an issue.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Productivity & Automation, covering Task management. It works with GitHub. The repository describes itself as: one page guides that i let my subscribed/customised agents consume to perform actions. The licence is Apache-2.0.
When your agent uses it
- The user says worklog
- Close a worklog
- Also use for issue-led development
- Umbrella issue tracking
Example prompts
- “worklog”
- “/worklog”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Inspect existing issues before creating new ones.
- Reuse an existing master issue if it clearly owns the effort.
- Create a new master issue when no durable parent exists.
- For every distinct work item, create or identify a child issue and link it from the master issue.
- If the task already has code changes in progress, inspect git status and diffs before deciding issue boundaries.
What it can do on your machine
Read from SKILL.md and the folder at commit a74dd9d. 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:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, 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
Worklog loads about 1.6k tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 692 words of instructions outside code blocks.
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 tokenbender/agent-guides at commit a74dd9d, republished under its Apache-2.0 licence (© tokenbender). 692 words, ~1,601 tokens.
Download SKILL.mdSave it as
.claude/skills/worklog/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- worklog
- description
- Issue-led atomic work logging. Use whenever the user says "worklog" or asks to run, apply, start, maintain, update, summarize, or close a worklog; also use for issue-led development, master or umbrella issue tracking, one-issue-per-bug/feature/change workflows, atomic issue-scoped commits, GitHub issue comment journals, closeout summaries, durable engineering ledgers, and making sure no compatibility, migration, cleanup, or residual-risk work is left hanging without an issue.
Worklog
Use GitHub issues as the durable source of truth for a body of work. Keep a master issue for the overall effort, a separate child issue for each bug, feature, experiment, or change, atomic commits for each logical unit, and issue comments as the running engineering ledger.
Core Contract
- Treat the master issue as the project ledger: scope, child issue index, current status, unresolved decisions, and final rollup.
- Treat child issues as executable work units: one bug, feature, experiment, refactor, docs change, or operational change per issue.
- Keep commits atomic and issue-scoped. Prefer one coherent commit per child issue or per independently reviewable step inside that issue.
- Record important observations, commands, failures, design decisions, implementation notes, artifacts, verification, and residual risk as comments on the child issue.
- Close a child issue only after posting a detailed closeout comment with what changed, evidence, tests, commit refs, and remaining follow-up.
- Update the master issue when child issues are opened, materially change direction, resolve, or create follow-up work.
- Do not leave hanging work implicit. If any compatibility shim, migration, cleanup, temporary fallback, unresolved verification, operational risk, or "duct tape" remains, create or link a follow-up issue before saying the work is done.
Before Touching GitHub
Verify the actual repo and target issue surface:
git remote -v
gh repo view --json nameWithOwner,url
gh issue list --state all --limit 50If the repo target is ambiguous, private/public boundaries are unclear, or the action would post to someone else's upstream repo, ask for confirmation before creating, commenting, closing, or editing issues. If a user fork exists and the user did not ask to post upstream, prefer the user's repo/fork.
Starting A Worklog
- Inspect existing issues before creating new ones.
- Reuse an existing master issue if it clearly owns the effort.
- Create a new master issue when no durable parent exists.
- For every distinct work item, create or identify a child issue and link it from the master issue.
- If the task already has code changes in progress, inspect
git statusand diffs before deciding issue boundaries.
Master issue body should include:
## Goal
<overall goal>
## Child issues
- [ ] #N - <title>
## Current state
<short status>
## Operating rule
Each bug, feature, experiment, or change gets its own issue. Work is recorded in issue comments. Commits stay atomic and issue-scoped. Child issues close with a detailed closeout; this master issue receives concise rollups.Child issue body should include:
## Scope
<one concrete unit of work>
## Why
<user-visible or engineering rationale>
## Acceptance criteria
- <verifiable outcome>
## Notes
Tracked under #<master-issue>.During Work
Post child issue comments at durable milestones, not for every minor thought:
- Initial diagnosis: what was observed, relevant files/issues, and the immediate plan.
- Important discoveries: new facts that change scope, risk, or approach.
- Implementation progress: atomic change made, files touched, and commit ref if available.
- Verification: exact commands run, pass/fail result, relevant output summary, and artifacts.
- Blockers: what failed, why it matters, and the proposed next move.
- Hardware profile gate for paid or long accelerator runs: before full launch, record the realistic smoke sweep, throughput, memory, estimated MFU, chosen profile, and any user-approved efficiency tradeoff.
Use comments as a journal another engineer could resume from. Include exact commands and paths when they are material. Avoid vague status updates that do not preserve new information.
Show full SKILL.md (225 more words)Show less
Atomic Commits
Before committing, inspect status and diffs:
git status --short
git diffStage narrowly. Do not include unrelated user changes. Commit messages should name the issue and the reason:
Fix share receiver timeout handling (#42)
Preserve captures when enrichment exceeds the fast-path budget so mobile sends
return promptly while background processing continues.If one diff covers multiple child issues, split it before committing when practical. If splitting would create churn or risk, explain the coupling in the issue comment and commit body.
Closing A Child Issue
Before closing, run a residual-work audit. Look specifically for compatibility aliases, temporary configs, local-only workarounds, migration gaps, unverified runtime surfaces, missing cleanup, security loosenings, flaky tests, manual steps, and known risks. If any remain, open or link issue(s) for them first.
Post a final comment before closing:
## Resolution
<what changed>
## Evidence
- Commit(s): <hashes or PR>
- Verification: <commands and results>
- Artifacts: <links or paths if relevant>
## Follow-up
<none, or linked issue numbers>Then close the issue. If follow-up work remains, open or link separate child issues instead of hiding incomplete work inside a closed issue. Only write none when the residual-work audit found no remaining tracked work.
Updating The Master Issue
When a child issue closes, post a concise master comment:
Resolved #N: <one-sentence outcome>.
Evidence: <commit/test/artifact summary>.
Follow-up: <none or linked issue numbers>.Keep the master issue useful for scanning. Detailed logs live on child issues; master comments are rollups and routing.
If GitHub Is Not Available
If gh is unavailable, authentication fails, or network access blocks issue updates, continue the workflow locally:
- Draft the exact issue body or comment text in the response.
- Preserve the child/master issue structure.
- Do not claim anything was posted.
- Tell the user what command or action remains.
© tokenbender, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in claude-skills/worklog of tokenbender/agent-guides.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit a74dd9d
Compare with similar skills
Worklog 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Worklog this skilltokenbender/agent-guides | 367 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Issue Progress Trackingyonatangross/orchestkit | 288 | — | ~1.1k | Automated safety check: Notes | MIT | |
| OpenObserve PR Briefopenobserve/openobserve | 22k | — | ~1.8k | Automated safety check: Pass | AGPL-3.0 | |
| Agent Kanban Task Workersaltbo/agent-kanban | 485 | — | ~855 | Automated safety check: Pass | Custom licence | |
| Release Kanban Mdantopolskiy/kanban-md | 223 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Pmcoreyhaines31/makerskills | 844 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
OpenObserve PR Brief
openobserve/openobserve
Produces a read-only morning brief of your open pull requests across the openobserve GitHub org, with a next step for each and a reminder for idle ones.
Agent Kanban Task Worker
saltbo/agent-kanban
Lets an agent read, claim, update and submit an assigned Agent Kanban task through the Realmroot Toolbox CLI, with progress notes and a review handoff.
Release Kanban Md
antopolskiy/kanban-md
Release kanban-md through its tag-triggered GoReleaser workflow, monitor CI, recover safely from failures, and publish user-facing GitHub release notes.
Pm
coreyhaines31/makerskills
When you want to manage projects across your businesses using a kanban + Eisenhower methodology.
Jira
magnus919/agent-skills
Interact with Atlassian Jira from the terminal: search issues with JQL, view details, create issues, add comments, count matches with fast approximate-count, list projects, discover valid…
More from tokenbender/agent-guides
All 11 skills in this repoCapability Horizon Estimator
tokenbender/agent-guides
Estimate whether an AI model can complete a task and how long it will take, using METR-style time-horizon modeling.
Technical Writing Workflow
tokenbender/agent-guides
A skill your agent uses for planning, researching, drafting, revising, or auditing technical write-ups, textbooks, papers, reports, READMEs, research notes, PR narratives, and public technical prose.
Epistemic Libido
tokenbender/agent-guides
Filter, compare, and rank papers, posts, captures, threads, bookmarks, product claims, or research ideas for high-entropy mechanistic insight and underpriced leverage.
Manim Math Explainer
tokenbender/agent-guides
Trigger when: (1) the user asks for Manim, Manim Community, or ManimCE, (2) code contains from manim import , or (3) the task is to build a mathematical explainer animation.
X Thread Reader
tokenbender/agent-guides
A skill your agent uses when the user provides an X/Twitter status URL and needs the full thread, context beyond the first post, comparison, summary, intent analysis, title extraction, or reliable…
Audit Sft Data Quality
tokenbender/agent-guides
Audit supervised fine-tuning datasets against the behavior and task they are meant to teach.
Related
Works with
Categories
Questions about Worklog
What does Worklog do?
Issue-led atomic work logging. An agent skill from tokenbender/agent-guides. Worklog is an agent skill from tokenbender/agent-guides. Issue-led atomic work logging.
When should I use Worklog?
Worklog fits situations like: the user says worklog; close a worklog; also use for issue-led development; umbrella issue tracking.
How do I install Worklog in Claude Code?
Run `npx skills add tokenbender/agent-guides --skill worklog -a claude-code`. Or copy the skill folder (claude-skills/worklog in tokenbender/agent-guides) into .claude/skills/worklog in your project. Claude Code loads it when a task matches its description.
How do I install Worklog in Codex?
Run `npx skills add tokenbender/agent-guides --skill worklog -a codex`. Or copy the skill folder (claude-skills/worklog in tokenbender/agent-guides) into .agents/skills/worklog in your project. Codex loads it when a task matches its description.
Can I use Worklog 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 tokenbender/agent-guides --skill worklog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/worklog, .gemini/skills/worklog, .github/skills/worklog and .opencode/skills/worklog in your project.
What does Worklog need to run?
Going by SKILL.md and its folder, Worklog needs the command-line tools its instructions call (git and gh).
Does Worklog access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Worklog 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 Worklog use?
Worklog is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Worklog use?
About 1.6k tokens (SKILL.md is roughly 6.4k 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 Worklog?
Skills that share tags, products or a category with Worklog: Issue Progress Tracking (yonatangross/orchestkit, 288 stars), OpenObserve PR Brief (openobserve/openobserve, 22k stars), Agent Kanban Task Worker (saltbo/agent-kanban, 485 stars) and Release Kanban Md (antopolskiy/kanban-md, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Worklog?
tokenbender (a GitHub user) maintains it in tokenbender/agent-guides, which has 367 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on July 23, 2026.
Source: tokenbender/agent-guides on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.