gemini-cli - ✅(Solved) Fix Gemini CLI should report how long it takes to load each skill [1 pull requests, 2 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25315Fetched 2026-04-14 05:56:01
View on GitHub
Comments
2
Participants
1
Timeline
11
Reactions
0
Participants
Timeline (top)
labeled ×4commented ×2mentioned ×2subscribed ×2

PR fix notes

PR #25373: Add verbose skill load timing diagnostics

Description (problem / solution / changelog)

Tries to address feature request #25315

Summary

Records skill discovery timing and shows it through verbose skill-listing flows. This first pass stays focused on reporting. It does not add client-side caching as suggested in the issue.

What changed

  • record per-directory discovery timing and per-skill load timing in the skill loader
  • expose that in /skills list verbose
  • keep normal startup/list output unchanged
  • add a /skills reload hint that points users to the verbose view when a slow skill load is detected

Architecture

High-level flow:

  1. SkillManager.discoverSkills() walks builtin, user, alias, and trusted workspace skill roots in order of precedence.
  2. Each root is loaded via loadSkillsFromDirWithReport(dir).
  3. The loader times the directory scan, runs glob() for SKILL.md, and loads each discovered skill file.
  4. Each load contributes a SkillLoadMetric, and each directory contributes a SkillDiscoveryReport.
  5. The latest in-memory reports drive /skills list verbose and reload guidance.

Validation

Automated:

  • npx vitest run src/skills/skillLoader.test.ts --coverage.enabled=false
  • npx vitest run src/ui/commands/skillsCommand.test.ts src/commands/skills/list.test.ts --coverage.enabled=false
  • npx tsc -p tsconfig.json --noEmit in packages/core
  • npx tsc -p tsconfig.json --noEmit in packages/cli

Manual:

  • verified /skills list verbose against local skills
  • verified /skills reload guidance when a slow skill is detected
  • validated the loader against a real remote SMB-backed skill root hosted on a GCP VM and accessed over Tailscale

Changed files

  • packages/cli/src/commands/skills/list.test.ts (modified, +57/-2)
  • packages/cli/src/commands/skills/list.ts (modified, +37/-10)
  • packages/cli/src/config/extension-manager.ts (modified, +7/-3)
  • packages/cli/src/ui/commands/skillsCommand.test.ts (modified, +66/-6)
  • packages/cli/src/ui/commands/skillsCommand.ts (modified, +18/-9)
  • packages/cli/src/ui/components/HistoryItemDisplay.tsx (modified, +1/-0)
  • packages/cli/src/ui/components/views/SkillsList.tsx (modified, +20/-4)
  • packages/cli/src/ui/types.ts (modified, +14/-1)
  • packages/cli/src/utils/skillDiscovery.test.ts (added, +49/-0)
  • packages/cli/src/utils/skillDiscovery.ts (added, +30/-0)
  • packages/core/src/commands/memory.ts (modified, +2/-2)
  • packages/core/src/config/config.ts (modified, +6/-0)
  • packages/core/src/skills/skillLoader.test.ts (modified, +126/-1)
  • packages/core/src/skills/skillLoader.ts (modified, +107/-13)
  • packages/core/src/skills/skillManager.test.ts (modified, +63/-0)
  • packages/core/src/skills/skillManager.ts (modified, +41/-6)
RAW_BUFFERClick to expand / collapse

Some users have Gemini CLI configured to load skills from a network share which can lead to delays during execution.

This issue tracks recording how long it takes to load each of these skills so the user can take action to remove them.

extent analysis

TL;DR

Tracking the load time of skills from a network share can help identify and remove slow-loading skills, improving Gemini CLI performance.

Guidance

  • Identify the skills loaded from the network share and measure their load times to pinpoint bottlenecks.
  • Consider relocating frequently used skills to a local storage to reduce load times.
  • Analyze the network share's performance and configuration to optimize access speeds.
  • Review user configurations to ensure they are not inadvertently causing delays.

Notes

The effectiveness of this approach depends on the specific network share and skill loading mechanisms used by the Gemini CLI.

Recommendation

Apply workaround: Tracking and optimizing skill load times can help mitigate performance issues without requiring significant changes to the Gemini CLI.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING