Agent skill

Working On

by posit-dev in posit-dev/skills

Set a tracking document as the source of truth for the current feature or task.

MITAuto-check passedDevelopment

Install Working On

skills CLI
$ npx skills add posit-dev/skills --skill working-on -a claude-code

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

GitHub CLI
$ gh skill install posit-dev/skills working-on --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/posit-dev/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/posit-dev/working-on .claude/skills/working-on && 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
working-on
GitHub stars
529
Token cost
~511 tokens
SKILL.md length
251 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Set a tracking document as the source of truth for the current feature or task.

  • Starting work on a feature
  • SKILL.md covers Behavior, Git Handling and Guidelines
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Multi-step task that benefits from a persistent record of decisions

What it does

Working On is an agent skill from posit-dev/skills. Set a tracking document as the source of truth for the current feature or task. Use when starting work on a feature, bug fix, or multi-step task that benefits from a persistent record of decisions, discoveries, and progress. Keeps the document updated as work proceeds.

Its SKILL.md is about 510 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, covering Debugging. The repository describes itself as: A collection of Claude Skills from Posit. The licence is MIT.

When your agent uses it

  • Starting work on a feature
  • Multi-step task that benefits from a persistent record of decisions

Example prompts

  • “/working-on”

What it can do on your machine

Read from SKILL.md and the folder at commit 0300946. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Working On loads about 511 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 251 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
~511

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 posit-dev/skills at commit 0300946, republished under its MIT licence (© posit-dev). 251 words, ~511 tokens.

Download SKILL.mdSave it as .claude/skills/working-on/SKILL.md (or your agent's skills folder).
name
working-on
description
Set a tracking document as the source of truth for the current feature or task. Use when starting work on a feature, bug fix, or multi-step task that benefits from a persistent record of decisions, discoveries, and progress. Keeps the document updated as work proceeds.
disable-model-invocation
true
arguments
path
argument-hint
[path-to-tracking-doc] [additional instructions]
metadata.author
Garrick Aden-Buie (@gadenbuie)
metadata.version
1.1
license
MIT

Working On

You are managing a tracking document that serves as the source of truth for the current task or feature.

The tracking document is: $path

Behavior

Once activated, treat the tracking document as a living record. Update it after:

  • Any decision is made (architectural, design, scope, naming, etc.)
  • A new problem, bug, or edge case is discovered
  • A new sub-feature or requirement emerges
  • An issue is raised or resolved
  • Any significant implementation work is completed
  • A key part of a conversation with the user that would be useful to recall later
  • Any time you commit files — a commit is a strong signal that the tracking document should also be reviewed and updated
  • Any plan you form — write it to the document rather than presenting it only in chat; the document is the persistent record

If in doubt, update the document. It is better to over-document than to lose context.

Git Handling

Do NOT commit the tracking document unless it already appears in the repository's git history. If the file is not tracked by git, leave it out of any commits.

Guidelines

  • Keep updates concise — bullet points and short paragraphs are preferred over prose
  • Use timestamps or date headers when the document spans multiple sessions
  • Record the why behind decisions, not just the what
  • When a section becomes stale or irrelevant, move it to an "Archive" or "Resolved" section rather than deleting it
  • If the document doesn't exist yet, create it with a sensible structure based on the task at hand

© posit-dev, 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 posit-dev/working-on of posit-dev/skills.

Open the folder on GitHubat commit 0300946

Compare with similar skills

Working On 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.

Working On compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Working On this skillposit-dev/skills529—~511Automated safety check: PassMIT
Trellis Session Insightmindfold-ai/Trellis15k4 repos~1.7kAutomated safety check: PassAGPL-3.0
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Aoti Debugpytorch/pytorch104k1 repos~1.7kAutomated safety check: PassCustom licence
Herdr Throwaway Reproductionherdrdev/herdr43k—~2.4kAutomated safety check: PassApache-2.0
Systematic Debuggingultralisp/ultralisp25851 repos~2.4kAutomated safety check: PassNone

Similar skills

  • Trellis Session Insight

    mindfold-ai/Trellis

    Reach into past AI conversation history through the trellis mem CLI.

    15k GitHub starsUsed in 4 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes
  • Aoti Debug

    pytorch/pytorch

    Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.

    104k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed
  • Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.

    43k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Systematic Debugging

    ultralisp/ultralisp

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    258 GitHub starsUsed in 51 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

More from posit-dev/skills

All 17 skills in this repo
  • R CLI App

    posit-dev/skills

    Build command-line apps in R using the Rapp package. An agent skill from posit-dev/skills.

    529 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • R Lifecycle

    posit-dev/skills

    Guidance for managing R package lifecycle according to tidyverse principles using the lifecycle package.

    529 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • PR Create

    posit-dev/skills

    Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes.

    529 GitHub stars~4.3k tokensUpdated yesterday
    Auto-check: warnings
  • Shiny Bslib

    posit-dev/skills

    Build modern Shiny dashboards and applications using bslib (Bootstrap 5).

    529 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Shiny Bslib Theming

    posit-dev/skills

    Advanced theming for Shiny apps using bslib and Bootstrap 5.

    529 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed
  • Critical Code Reviewer

    posit-dev/skills

    Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases.

    529 GitHub stars~3.9k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Working On

What does Working On do?

Set a tracking document as the source of truth for the current feature or task. Working On is an agent skill from posit-dev/skills. Set a tracking document as the source of truth for the current feature or task.

When should I use Working On?

Working On fits situations like: starting work on a feature; multi-step task that benefits from a persistent record of decisions.

How do I install Working On in Claude Code?

Run `npx skills add posit-dev/skills --skill working-on -a claude-code`. Or copy the skill folder (posit-dev/working-on in posit-dev/skills) into .claude/skills/working-on in your project. Claude Code loads it when a task matches its description.

How do I install Working On in Codex?

Run `npx skills add posit-dev/skills --skill working-on -a codex`. Or copy the skill folder (posit-dev/working-on in posit-dev/skills) into .agents/skills/working-on in your project. Codex loads it when a task matches its description.

Can I use Working On 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 posit-dev/skills --skill working-on -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/working-on, .gemini/skills/working-on, .github/skills/working-on and .opencode/skills/working-on in your project.

What does Working On need to run?

SKILL.md names no scripts, command-line tools or credentials: Working On is instructions for the agent only.

Does Working On access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Working On 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 Working On use?

Working On is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Working On use?

About 511 tokens (SKILL.md is roughly 2k 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 Working On?

Skills that share tags, products or a category with Working On: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Aoti Debug (pytorch/pytorch, 104k stars) and Herdr Throwaway Reproduction (herdrdev/herdr, 43k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Working On?

posit-dev (a GitHub organization) maintains it in posit-dev/skills, which has 529 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.

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