Agent skill · Data & Analytics

eta

When a user asks how long a task will take, requests a time estimate, or before starting any non-trivial coding task, immediately run scripts/estimate_task.py to analyze the codebase scope and provide a data-driven time estimate. Show the estimate breakdown, risk factors, and checkpoint recommendations without asking.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill eta --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: none
Path: skills/analysis/eta/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# ETA <purpose> Provides realistic time estimates for coding tasks before work begins. Users often underestimate task complexity. This skill analyzes codebase scope, categorizes task complexity, identifies risk factors, and calculates estimates based on measured Claude Code performance baselines. Prevents surprise delays and enables better planning. </purpose> ## Instructions ### Step 1: Gather Task Context When triggered, collect: - Task description from the user - Path to relevant codebase (default: current directory) - Number of files likely in scope (if known) ### Step 2: Run Estimation ```bash python scripts/estimate_task.py --task "<task_description>" --path "<codebase_path>" ``` Optional flags: - `--files <n>`: Override estimated files in scope - `--json`: Output structured JSON for programmatic use ### Step 3: Present Estimate Return the formatted estimate showing: - Task category (trivial/simple/medium/complex/major) - Scope analysis (files, lines, test coverage) - Time range (low-high estimate) - Breakdown by phase (analysis, implementation, testing, verification) - Risk factors with explanations - Checkpoint recommendations for long tasks ### Step 4: Adjust Based on Feed

What's inside
Steps it walks through
  1. Instructions
  2. Step 1: Gather Task Context
  3. Step 2: Run Estimation
  4. Step 3: Present Estimate
  5. Step 4: Adjust Based on Feedback
  6. NEVER
  7. ALWAYS
  8. Examples
  9. Example 1: User asks about task duration
  10. Example 2: Before starting a feature
  11. Example 3: Quick fix request
Ships with 1 file
  • metadata.json
Commands it runs
python scripts/estimate_task.py --task "<task_description>" --path "<codebase_path>"
More from claude-skill-registry
All skills →
About this skill
What does the eta skill do?

When a user asks how long a task will take, requests a time estimate, or before starting any non-trivial coding task, immediately run scripts/estimate_task.py to analyze the codebase scope and provide a data-driven time estimate. Show the estimate breakdown, risk factors, and checkpoint recommendations without asking.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill eta --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going