docs: document .agents/skills alias and discovery precedence#19166
docs: document .agents/skills alias and discovery precedence#19166NTaylorMullen merged 1 commit intogoogle-gemini:mainfrom
Conversation
Update documentation to reflect the support for the .agents/skills directory alias in both user and workspace tiers. - Add precedence details (.agents/skills > .gemini/skills). - Update shell command examples to include both paths. - Add notes to the 'Getting Started' guide.
Summary of ChangesHello @kevmoo, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the documentation for the Gemini CLI to accurately reflect recent changes in how skills are discovered. It clarifies the introduction of the Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the documentation to include the new .agents/skills directory alias for skill discovery, including details on its precedence. The changes are generally clear and align with the feature. The comment regarding ambiguity in docs/cli/skills.md for install and link commands has been retained as it provides valuable feedback for improving documentation precision and user experience, and does not conflict with any provided rules.
| # Discovers skills (SKILL.md or */SKILL.md) and creates symlinks in ~/.gemini/skills | ||
| # (or ~/.agents/skills) | ||
| gemini skills link /path/to/my-skills-repo | ||
|
|
||
| # Link to the workspace scope (.gemini/skills) | ||
| # Link to the workspace scope (.gemini/skills or .agents/skills) | ||
| gemini skills link /path/to/my-skills-repo --scope workspace | ||
|
|
||
| # Install a skill from a Git repository, local directory, or zipped skill file (.skill) | ||
| # Uses the user scope by default (~/.gemini/skills) | ||
| # Uses the user scope by default (~/.gemini/skills or ~/.agents/skills) | ||
| gemini skills install https://github.com/user/repo.git | ||
| gemini skills install /path/to/local/skill | ||
| gemini skills install /path/to/local/my-expertise.skill | ||
|
|
||
| # Install a specific skill from a monorepo or subdirectory using --path | ||
| gemini skills install https://github.com/my-org/my-skills.git --path skills/frontend-design | ||
|
|
||
| # Install to the workspace scope (.gemini/skills) | ||
| # Install to the workspace scope (.gemini/skills or .agents/skills) | ||
| gemini skills install /path/to/skill --scope workspace |
There was a problem hiding this comment.
The comments for the link and install commands are ambiguous. Using (or .agents/skills) doesn't clarify which directory is used or when. This could lead to user confusion about where their skills are being installed or linked.
Please specify the exact behavior. For example:
- Does one path take precedence? (e.g.,
...in ~/.agents/skills, falling back to ~/.gemini/skills) - Does the command use whichever directory already exists?
- Is the new
.agents/skillspath now the default for all new installations/links?
Clarifying this logic will make the documentation much more helpful.
gemini-cli
bot
added
status/need-issue
d1ca8c0
2 participants
Summary
Document the
.agents/skillsdirectory alias and its precedence logic in the agent skills documentation.Details
This PR updates the agent skills documentation to include information about the
.agents/skillsdirectory alias, which was introduced to provide a more generic and intuitive path for managing agent-specific expertise. It also clarifies that.agents/skillstakes precedence over.gemini/skillswithin the same tier (user or workspace).Changes:
docs/cli/skills.mdwith tier-specific alias information and precedence rules.docs/cli/tutorials/skills-getting-started.mdto mention the alias as an alternative..gemini/skillsand.agents/skillspaths.Related Issues
Closes #19167
How to Validate
docs/cli/skills.mddocs/cli/tutorials/skills-getting-started.mdpackages/core/src/skills/skillManager.ts.Pre-Merge Checklist