Agent skill

Tracking Doc Worker

by CorrectRoadH in CorrectRoadH/OpenTickly

Audit and finalize inline source-document status blocks for the timer refactor mission.

AGPL-3.0Auto-check passed

Install Tracking Doc Worker

skills CLI
$ npx skills add CorrectRoadH/OpenTickly --skill tracking-doc-worker -a claude-code

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

GitHub CLI
$ gh skill install CorrectRoadH/OpenTickly tracking-doc-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/CorrectRoadH/OpenTickly.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.factory/skills/tracking-doc-worker .claude/skills/tracking-doc-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
tracking-doc-worker
GitHub stars
306
Token cost
~819 tokens
SKILL.md length
241 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Audit and finalize inline source-document status blocks for the timer refactor mission.

  • Works in 8 steps: Read mission mission.md, mission… → Treat the closed source-doc list in… → Read the relevant completed feature… → …
  • SKILL.md covers When to Use This Skill, Required Skills, Work Procedure and Example Handoff, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tracking Doc Worker is an agent skill from CorrectRoadH/OpenTickly. Audit and finalize inline source-document status blocks for the timer refactor mission.

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

The repository describes itself as: Self-hosted, Toggl-compatible time tracker. The licence is AGPL-3.0.

Example prompts

  • “/tracking-doc-worker”

Workflow steps

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

  1. Read mission mission.md, mission AGENTS.md, .factory/library/documentation-traceability.md, and the current features.json.
  2. Treat the closed source-doc list in mission AGENTS.md as canonical. Do not audit docs outside that list unless the orchestrator changes it…
  3. Read the relevant completed feature handoffs or verification evidence so the status blocks describe the real final implementation state.
  4. Add or update exactly one active mission status block in each listed source doc.
  5. Use the canonical field labels exactly
  6. Keep the blocks honest
  7. Run the traceability validation command from .factory/services.yaml after the edits.
  8. In the handoff, explicitly state

What it can do on your machine

Read from SKILL.md and the folder at commit 5ffd0a0. 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 (its code samples are json).

    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

Tracking Doc Worker loads about 819 tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 241 words of instructions outside code blocks.

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

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 CorrectRoadH/OpenTickly at commit 5ffd0a0, republished under its AGPL-3.0 licence (© CorrectRoadH). 241 words, ~819 tokens.

Download SKILL.mdSave it as .claude/skills/tracking-doc-worker/SKILL.md (or your agent's skills folder).
name
tracking-doc-worker
description
Audit and finalize inline source-document status blocks for the timer refactor mission.

Tracking Doc Worker

NOTE: Startup and cleanup are handled by worker-base. This skill defines the work procedure.

When to Use This Skill

Use for features that primarily update or audit the inline status blocks in the closed set of implementation-driving source docs.

Required Skills

None.

Work Procedure

  1. Read mission mission.md, mission AGENTS.md, .factory/library/documentation-traceability.md, and the current features.json.
  2. Treat the closed source-doc list in mission AGENTS.md as canonical. Do not audit docs outside that list unless the orchestrator changes it first.
  3. Read the relevant completed feature handoffs or verification evidence so the status blocks describe the real final implementation state.
  4. Add or update exactly one active mission status block in each listed source doc.
  5. Use the canonical field labels exactly:
    • Agent
    • Status
    • Current code differences
    • Todo
    • Fully implemented
  6. Keep the blocks honest:
    • if work remains, do not mark Fully implemented: yes
    • if Todo is none, the remaining fields must also describe a landed state
  7. Run the traceability validation command from .factory/services.yaml after the edits.
  8. In the handoff, explicitly state:
    • which docs were updated
    • whether any listed doc still has open gaps
    • why each Fully implemented value is truthful

Example Handoff

json
{
  "salientSummary": "Updated the inline mission status blocks across the closed timer source-doc set and verified the canonical fields and consistency rules. The blocks now reflect which timer docs are fully landed versus which still describe open implementation gaps.",
  "whatWasImplemented": "Added or refreshed one active mission status block in each directly used timer source document listed in mission `AGENTS.md`, using the canonical field schema and aligning every block with the verified implementation state from the completed features. Ran the repo traceability check to confirm field presence and block coverage.",
  "whatWasLeftUndone": "",
  "verification": {
    "commandsRun": [
      {
        "command": "rg -n \"Mission status|Agent:|Status:|Current code differences:|Todo:|Fully implemented:\" docs/product/tracking.md docs/research/toggl-timer-*.md",
        "exitCode": 0,
        "observation": "Every listed source doc exposed one mission status block with the canonical field names."
      }
    ],
    "interactiveChecks": [
      {
        "action": "Manually reviewed each listed source doc against the final feature evidence.",
        "observed": "The status blocks matched the verified implementation state and no doc marked itself fully implemented while still listing open todo items."
      }
    ]
  },
  "tests": {
    "added": []
  },
  "discoveredIssues": []
}

When to Return to Orchestrator

  • A required source doc is missing from the closed list in mission AGENTS.md
  • The final implementation evidence is too incomplete to write truthful status blocks
  • The task reveals contradictions between completed feature claims and the actual landed implementation state

© CorrectRoadH, AGPL-3.0. 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 .factory/skills/tracking-doc-worker of CorrectRoadH/OpenTickly.

Open the folder on GitHubat commit 5ffd0a0

Compare with similar skills

Tracking Doc 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.

Tracking Doc Worker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tracking Doc Worker this skillCorrectRoadH/OpenTickly306—~819Automated safety check: PassAGPL-3.0
Docnexu-io/open-design100k—~266Automated safety check: PassApache-2.0
Docsremotion-dev/remotion62k—~248Automated safety check: PassCustom licence
Update Docsvercel/next.js143k—~1.9kAutomated safety check: PassMIT
DocsPrefectHQ/fastmcp28k—~1kAutomated safety check: PassApache-2.0
Docs Diagramsvercel/next.js143k—~2.9kAutomated safety check: PassMIT

Similar skills

  • Doc

    nexu-io/open-design

    Read, create, and edit .docx documents with formatting and layout fidelity via OpenAI's document skill.

    100k GitHub stars~266 tokensUpdated today
    Documents & OfficeAuto-check passed
  • Docs

    remotion-dev/remotion

    Official

    Start the Remotion docs site and open it in the Codex browser.

    62k GitHub stars~248 tokensUpdated today
    Media & CreativeAuto-check passed
  • Update Docs

    vercel/next.js

    Official

    This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature"…

    143k GitHub stars~1.9k tokensUpdated today
    Documents & OfficeAuto-check passed
  • Docs

    PrefectHQ/fastmcp

    Write or revise a page under docs/ for gofastmcp.com. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~1k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Docs Diagrams

    vercel/next.js

    Official

    Draw diagrams for the Next.js docs in the style of the ones already published there: the light/dark PNGs an mdx references with <Image srcLight="/docs/light/<name.png" srcDark="/docs/dark/<name.png".

    143k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Docs Artifact

    asgeirtj/system_prompts_leaks

    A skill your agent uses when creating, editing, or reviewing a document for the user (Word, Google Docs, or a document delivered as PDF), or when the task calls for a standalone written deliverable…

    69k GitHub stars~1.5k tokensUpdated today
    Documents & OfficeAuto-check passed

More from CorrectRoadH/OpenTickly

All 10 skills in this repo
  • Backend Test Worker

    CorrectRoadH/OpenTickly

    Build and verify real-Postgres Go tests and thin transport smoke for tracking behavior.

    306 GitHub stars~1.3k tokensUpdated 6 days ago
    Auto-check passed
  • Frontend Test Worker

    CorrectRoadH/OpenTickly

    Build and verify page-flow and E2E coverage for the tracking browser surface.

    306 GitHub stars~1.4k tokensUpdated 6 days ago
    Auto-check passed
  • Fullstack Regression Worker

    CorrectRoadH/OpenTickly

    Build cross-layer regression coverage that ties browser-visible behavior to backend truth.

    306 GitHub stars~1.1k tokensUpdated 6 days ago
    Auto-check passed
  • Test Platform Worker

    CorrectRoadH/OpenTickly

    Harden shared test infrastructure, runtime readiness, schema setup, and parallel lane behavior.

    306 GitHub stars~1.2k tokensUpdated 6 days ago
    Auto-check passed
  • Tracking Backend Worker

    CorrectRoadH/OpenTickly

    Update backend timer/time-entry contracts, regressions, and source docs for the timer refactor mission.

    306 GitHub stars~1.2k tokensUpdated 6 days ago
    Auto-check passed
  • Tracking Frontend Worker

    CorrectRoadH/OpenTickly

    Refactor and verify website timer/time-entry surfaces on the reused local runtime.

    306 GitHub stars~1.2k tokensUpdated 6 days ago
    Auto-check passed

Questions about Tracking Doc Worker

What does Tracking Doc Worker do?

Audit and finalize inline source-document status blocks for the timer refactor mission. Tracking Doc Worker is an agent skill from CorrectRoadH/OpenTickly. Audit and finalize inline source-document status blocks for the timer refactor mission.

How do I install Tracking Doc Worker in Claude Code?

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

How do I install Tracking Doc Worker in Codex?

Run `npx skills add CorrectRoadH/OpenTickly --skill tracking-doc-worker -a codex`. Or copy the skill folder (.factory/skills/tracking-doc-worker in CorrectRoadH/OpenTickly) into .agents/skills/tracking-doc-worker in your project. Codex loads it when a task matches its description.

Can I use Tracking Doc 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 CorrectRoadH/OpenTickly --skill tracking-doc-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/tracking-doc-worker, .gemini/skills/tracking-doc-worker, .github/skills/tracking-doc-worker and .opencode/skills/tracking-doc-worker in your project.

What does Tracking Doc Worker need to run?

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

Does Tracking Doc Worker 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 Tracking Doc 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 Tracking Doc Worker use?

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

How many tokens does Tracking Doc Worker use?

About 819 tokens (SKILL.md is roughly 3.3k 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 Tracking Doc Worker?

Skills that share tags, products or a category with Tracking Doc Worker: Doc (nexu-io/open-design, 100k stars), Docs (remotion-dev/remotion, 62k stars), Update Docs (vercel/next.js, 143k stars) and Docs (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tracking Doc Worker?

CorrectRoadH (a GitHub user) maintains it in CorrectRoadH/OpenTickly, which has 306 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 2, 2026.

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