Enable and check a Gemini CLI skill

Goal

Make a reviewed skill discoverable in the intended Gemini CLI workspace and check its matching behavior.

Steps

1. Read the current Gemini CLI skill guide and note the precedence of built-in, extension, user, and workspace locations. [gemini-skill-guide]
2. Inspect the repository's SKILL.md, scripts, and assets; place the reviewed files in the user-level or workspace-level skill directory. [gemini-skill-guide]
3. If using gemini skills install, verify the URL and repository owner, then confirm the installation scope before running it. [gemini-skill-guide]
4. In a CLI session, run /skills list and confirm the expected name appears; check precedence if names collide. [gemini-skill-guide]
5. Try a request within the skill's scope and a neighboring request outside it to check activation boundaries. [gemini-skill-guide]
6. Check the documentation for the target Gemini CLI version and confirm its discovery rules and duplicate-name precedence. Then use that product version’s documented list or reload command. Testing matching and non-matching requests is an extra product-behavior check, not a triggering rule guaranteed by the open format specification. [gemini-skill-guide] [gemini-config]

How to verify

The session list includes the expected skill, and matching/non-matching requests behave as intended; a listed name does not prove that bundled scripts are harmless.

Troubleshooting

Refresh discovery with `/skills reload`. If the skill is missing, check its directory, duplicate-name precedence, CLI version, and `skills.enabled` configuration.