Agent skill · data analytics · google-gemini
effort
Estimates the implementation effort required to address the given issue.
Why this skill is useful
Provides a structured approach to estimating implementation effort, which includes domain-specific criteria for categorizing issues.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 106,400 stars on the source repository.
What this skill does
Effort Estimator Instructions Analyze the issue content (title, body) AND the code exploration output (the discovered source files, coupled UI components, and test files) to estimate the effort required to implement a fix. JSON Output Format: Effort Levels: SMALL (1 day or less): Trivial Logic & Config: Schema updates (Zod), feature flag toggles, adding missing fields to package.json or settings.json. UI/Aesthetic Adjustments: Fixing minor layout bugs in Ink components (e.g., adding flexShrink, correcting padding in a single Box), text color changes. Documentation & Strings: Typos, log message updates, CLI argument descriptions. Localized Bug Fixes: Single-file logic errors, straightforward promise rejections (e.g., wrapping a known failure in a try/catch), simple regex or string parsing fixes. Unhandled Errors with Obvious Fixes: Issues with provided stack traces or obvious offending lines where the root cause and fix are clear. MEDIUM (2-3 days): React/Ink State Management: Complex component lifecycle issues (memory leaks in the UI), terminal redraw flickering, or state synchronization between the CLI's internal input buffer and the interactive React components. Asynchronous Flow & Integration: Resolving complex Promise chains, ERRSTREAMPREMATURECLOSE, debugging IDE companion extensions (VS Code, Android Studio) or resolving hanging HTTP requests/IPC between the CLI and external plugins, timeouts in non-interactive/ACP modes. Tooling & Output Parsers: Modifying how tools parse streaming stdout/stderr buffers, adding new built-in tools that don't require native bindings. Cross-Component & Cross-Package Refactors: Any fix or change that spans across packages/cli and packages/core (such as unifying event handlers, hooks, or UI state across package boundaries). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google-gemini/effort