New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Report Progress Eta Analyze

by swyxio in swyxio/skills

Summarize progress, estimate completion from remaining work and observed timings, explain forecast changes, and identify measured inefficiencies.

MITAuto-check passed

Install Report Progress Eta Analyze

skills CLI
$ npx skills add swyxio/skills --skill report-progress-eta-analyze -a claude-code

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

GitHub CLI
$ gh skill install swyxio/skills report-progress-eta-analyze --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/swyxio/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/report-progress-eta-analyze .claude/skills/report-progress-eta-analyze && 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
report-progress-eta-analyze
GitHub stars
176
Token cost
~1.4k tokens
SKILL.md length
752 words
Files
1
Skills in repo
89
Repo updated
First seen
Licence
MIT

At a glance

Summarize progress, estimate completion from remaining work and observed timings, explain forecast changes, and identify measured inefficiencies.

  • Works in 6 steps: List unfinished stages, remaining units,… → Estimate each stage from comparable… → Account for work already spent in an… → …
  • Status and ETA requests
  • SKILL.md covers Establish progress and…, Build and revise the ETA, Report the useful summary and Observe inefficiencies
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Report Progress Eta Analyze is an agent skill from swyxio/skills. Summarize progress, estimate completion from remaining work and observed timings, explain forecast changes, and identify measured inefficiencies. Use for status and ETA requests or progress reports on multi-stage work such as batches, builds, research, migrations and releases. Does not launch, schedule or modify the work being reported.

Its SKILL.md is about 1.4k 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: Agent skills for Claude Code and other AI agents. The licence is MIT.

When your agent uses it

  • Status and ETA requests
  • Progress reports on multi-stage work such as batches
  • Migrations and releases

Example prompts

  • “/report-progress-eta-analyze”

Workflow steps

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

  1. List unfinished stages, remaining units, dependencies and current active/queued work. Include finishing work such as assembly, review…
  2. Estimate each stage from comparable retained timings, preferring the current run, then recent runs with similar input size, model…
  3. Account for work already spent in an active stage without restarting its full estimate at every heartbeat. If it has exceeded comparable…
  4. Follow the dependency path to completion: add sequential stages and use the longest overlapping branch at joins. Account for branches…
  5. Give a likely remaining range and, when useful, a completion window in the user's timezone. State the assumptions and dominant…
  6. Compare with the previous forecast and the original baseline. Explain material movement with concrete causes: new scope, slower service…

What it can do on your machine

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

Report Progress Eta Analyze loads about 1.4k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 752 words of instructions outside code blocks.

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

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 swyxio/skills at commit 038ef34, republished under its MIT licence (© swyxio). 752 words, ~1,401 tokens.

Download SKILL.mdSave it as .claude/skills/report-progress-eta-analyze/SKILL.md (or your agent's skills folder).
name
report-progress-eta-analyze
description
Summarize progress, estimate completion from remaining work and observed timings, explain forecast changes, and identify measured inefficiencies. Use for status and ETA requests or progress reports on multi-stage work such as batches, builds, research, migrations and releases. Does not launch, schedule or modify the work being reported.

Report Progress, ETA, and Analyze

Use existing plans, process state, logs, results and timing receipts to explain how close the authorized outcome is to completion. Refresh cheap, time-sensitive evidence when available; distinguish current observations, older receipts, estimates and unknowns. Reuse the existing run artifacts rather than introducing another ledger or telemetry system.

Establish progress and remaining work

Report the state of the whole authorized outcome, not just the last command or heartbeat. Lead with what is complete, what remains and the current bottleneck. Distinguish generated, accepted, released and live-verified output. When work has separate deliverables, such as a code release and a content pilot, give each its own state and forecast. Counts of passing tests or completed model calls are supporting evidence, not a percentage of the whole task.

Build and revise the ETA

Build the forecast from remaining work before giving a completion time:

  1. List unfinished stages, remaining units, dependencies and current active/queued work. Include finishing work such as assembly, review, release and live verification, not only generation.
  2. Estimate each stage from comparable retained timings, preferring the current run, then recent runs with similar input size, model, configuration and effective concurrency. Record the evidence source and sample count. For queues use observed accepted throughput, not the configured slot ceiling. Where evidence is sparse, give a labeled provisional range; where no defensible estimate exists, say unavailable.
  3. Account for work already spent in an active stage without restarting its full estimate at every heartbeat. If it has exceeded comparable durations, inspect progress and revise the explanation rather than clamping remaining time to zero. Separate normal work, known queue/cooldown waits and expected repair overhead supported by observations.
  4. Follow the dependency path to completion: add sequential stages and use the longest overlapping branch at joins. Account for branches sharing constrained capacity; do not assume they overlap perfectly or add all worker durations as wall time.
  5. Give a likely remaining range and, when useful, a completion window in the user's timezone. State the assumptions and dominant uncertainty. An unresolved external hold makes the unconditional finish time unknown; still estimate independent work and the remaining work after clearance when evidence supports it. Never invent a provider recovery time or hide the rest of the task behind “blocked.”
  6. Compare with the previous forecast and the original baseline. Explain material movement with concrete causes: new scope, slower service, lost concurrency, a repair, queue time or duplicated validation. Preserve earlier estimates so each wakeup does not silently move the deadline. At completion, retain estimated versus actual stage durations for future calibration.
Show full SKILL.md (323 more words)Show less

Report the useful summary

Use this compact shape for meaningful updates, adapting it to the task:

  • Progress: accepted/delivered scope versus total; major completed milestones and total elapsed time.
  • Since the last update: the consequential change and its effect on completion or quality.
  • Remaining: the next stages, which can overlap, and the critical blocker or bottleneck.
  • ETA: remaining range, comparison with the previous estimate, and a short evidence basis. Separate conditional completion from unknown external waits.
  • Next action: what is being done to advance or unblock the work; whether the user needs to act.

Keep the detailed timing breakdown in existing run artifacts and link it when useful. A short remaining-stage table is appropriate when several branches make the estimate hard to follow. Do not dump raw counters or repeat that the monitor is active. Answer an explicit status request even when unchanged, stating how fresh the evidence is. For scheduled reporting, follow the existing notification cadence and stay quiet when there is no meaningful change in progress, forecast, risk or required action. This skill does not create a monitor.

Observe inefficiencies

End the analysis with a brief look for avoidable delay: idle capacity with ready work, unnecessary serial dependencies, repeated checks or builds, redundant model calls, excessive retries, and coordination overhead. Distinguish necessary quality/release gates from duplicated work; a long duration alone does not prove waste.

Surface only the most consequential evidenced finding or two. State the observation, its likely effect on the critical path, and the smallest improvement worth trying. Quantify recoverable time only when the data supports it; otherwise label the idea unmeasured. Track whether a prior intervention actually helped. If there is no meaningful finding, omit this from the user-facing report.

Analysis does not itself authorize pausing jobs, changing concurrency or refactoring. An already-authorized supervisor can use the finding to act through babysit-runs; otherwise present it as a recommendation. Do not turn a progress request into an open-ended optimization project.

© swyxio, 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 report-progress-eta-analyze of swyxio/skills.

Open the folder on GitHubat commit 038ef34

Compare with similar skills

Report Progress Eta Analyze 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.

Report Progress Eta Analyze compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Report Progress Eta Analyze this skillswyxio/skills176—~1.4kAutomated safety check: PassMIT
Progressive Estimationsickn33/agentic-awesome-skills47k2 repos~863Automated safety check: PassMIT
Summarizeopenclaw/openclaw392k1 repos~531Automated safety check: PassMIT
Langsmith ObservabilityOrchestra-Research/AI-Research-SKILLs13k2 repos~2.4kAutomated safety check: PassMIT
ObservabilityBuilderIO/agent-native7.1k—~7.3kAutomated safety check: PassNone
Frontend Observabilitysickn33/agentic-awesome-skills47k1 repos~5.1kAutomated safety check: PassMIT

Similar skills

  • Progressive Estimation

    sickn33/agentic-awesome-skills

    Estimate AI-assisted and hybrid human+agent development work with research-backed PERT statistics and calibration feedback loops

    47k GitHub starsUsed in 2 repos~863 tokens
    Data & AnalyticsAuto-check passed

  • Summarize

    openclaw/openclaw

    Summarize or transcribe URLs, YouTube/videos, podcasts, articles, transcripts, PDFs, and local files.

    392k GitHub starsUsed in 1 repo~531 tokens
    Media & CreativeAuto-check passed

  • Langsmith Observability

    Orchestra-Research/AI-Research-SKILLs

    LLM observability platform for tracing, evaluation, and monitoring.

    13k GitHub starsUsed in 2 repos~2.4k tokens
    AI & LLM EngineeringAuto-check passed

  • Observability

    BuilderIO/agent-native

    Agent observability, evals, feedback, and experiments. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~7.3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Frontend Observability

    sickn33/agentic-awesome-skills

    A portable, framework-agnostic field-side observability system for any React or React Native app.

    47k GitHub starsUsed in 1 repo~5.1k tokens
    DevOps & CloudAuto-check passed

  • Ebpf Observability

    sickn33/agentic-awesome-skills

    Use eBPF for deep kernel-level observability — trace syscalls, network flows, and application behavior without code changes using Cilium, Tetragon, and bpftrace.

    47k GitHub starsUsed in 2 repos~3.3k tokens
    DevOps & CloudAuto-check: notes

More from swyxio/skills

All 89 skills in this repo

  • Programmatic Agents

    swyxio/skills

    Run a selected coding-agent CLI programmatically, with latency, error, usage, cost, and trace logging.

    176 GitHub stars~2.2k tokensUpdated 5 days ago
    Auto-check passed

  • Reserved Handle Policy

    swyxio/skills

    Design, implement, audit, or refresh protected username and handle namespaces for public products.

    176 GitHub stars~1.1k tokensUpdated 5 days ago
    Auto-check passed

  • New Mac Setup

    swyxio/skills

    Fully automated new Mac setup for fullstack web developers and AI engineers.

    176 GitHub stars~4.3k tokensUpdated 5 days ago
    Auto-check passed

  • Youtube API

    swyxio/skills

    Manage YouTube videos programmatically via the YouTube Data API v3 — upload video files, upload custom thumbnails, update video metadata (titles, descriptions, tags), and query video/channel info…

    176 GitHub stars~2.2k tokensUpdated 5 days ago
    Auto-check passed

  • Youtube Studio Batch Upload

    swyxio/skills

    Batch YouTube Studio upload workflow for videos sourced from Airtable, Google Drive, Loom, YouTube, or local files.

    176 GitHub stars~1.5k tokensUpdated 5 days ago
    Auto-check: warnings

  • Deep Trajectory Analysis

    swyxio/skills

    Reconstruct and visually analyze paired agent, game, or policy trajectories to determine whether changed actions produced their intended effects.

    176 GitHub stars~1.8k tokensUpdated 5 days ago
    Auto-check passed

Questions about Report Progress Eta Analyze

What does Report Progress Eta Analyze do?

Summarize progress, estimate completion from remaining work and observed timings, explain forecast changes, and identify measured inefficiencies. Report Progress Eta Analyze is an agent skill from swyxio/skills. Summarize progress, estimate completion from remaining work and observed timings, explain forecast changes, and identify measured inefficiencies.

When should I use Report Progress Eta Analyze?

Report Progress Eta Analyze fits situations like: status and ETA requests; progress reports on multi-stage work such as batches; migrations and releases.

How do I install Report Progress Eta Analyze in Claude Code?

Run `npx skills add swyxio/skills --skill report-progress-eta-analyze -a claude-code`. Or copy the skill folder (report-progress-eta-analyze in swyxio/skills) into .claude/skills/report-progress-eta-analyze in your project. Claude Code loads it when a task matches its description.

How do I install Report Progress Eta Analyze in Codex?

Run `npx skills add swyxio/skills --skill report-progress-eta-analyze -a codex`. Or copy the skill folder (report-progress-eta-analyze in swyxio/skills) into .agents/skills/report-progress-eta-analyze in your project. Codex loads it when a task matches its description.

Can I use Report Progress Eta Analyze 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 swyxio/skills --skill report-progress-eta-analyze -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/report-progress-eta-analyze, .gemini/skills/report-progress-eta-analyze, .github/skills/report-progress-eta-analyze and .opencode/skills/report-progress-eta-analyze in your project.

What does Report Progress Eta Analyze need to run?

SKILL.md names no scripts, command-line tools or credentials: Report Progress Eta Analyze is instructions for the agent only.

Does Report Progress Eta Analyze 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 Report Progress Eta Analyze 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 Report Progress Eta Analyze use?

Report Progress Eta Analyze 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 Report Progress Eta Analyze use?

About 1.4k tokens (SKILL.md is roughly 5.6k 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 Report Progress Eta Analyze?

Skills that share tags, products or a category with Report Progress Eta Analyze: Progressive Estimation (sickn33/agentic-awesome-skills, 47k stars), Summarize (openclaw/openclaw, 392k stars), Langsmith Observability (Orchestra-Research/AI-Research-SKILLs, 13k stars) and Observability (BuilderIO/agent-native, 7.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Report Progress Eta Analyze?

swyxio (a GitHub user) maintains it in swyxio/skills, which has 176 GitHub stars. The repository holds 89 skills in this directory. The repository was last updated on October 5, 2026.

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