gemini
Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Uses Gemini 3 Pro by default for state-of-the-art reasoning and coding.
84
76%
Does it follow best practices?
Impact
100%
1.66xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./dist/plugins/gemini/skills/gemini/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has a clear 'Use when' clause and establishes a distinct niche around Gemini CLI and large context processing. However, it could be more specific about concrete actions beyond 'comprehensive analysis' and include more natural trigger term variations that users might actually say.
Suggestions
Add more specific concrete actions beyond 'comprehensive analysis' - e.g., 'analyze large codebases', 'review lengthy documents', 'process files exceeding Claude's context'
Include additional natural trigger terms users might say: 'Gemini', 'large file', 'long document', 'external model', 'big codebase'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gemini CLI) and some actions (code review, plan review, big context processing), but lacks comprehensive concrete actions. 'Comprehensive analysis' is somewhat vague. | 2 / 3 |
Completeness | Clearly answers both what (run Gemini CLI for code review, plan review, big context processing) and when (explicit 'Use when' clause with specific triggers including context size threshold). | 3 / 3 |
Trigger Term Quality | Includes some natural terms like 'code review', 'plan review', and '>200k' context, but missing common variations users might say like 'large file', 'long document', 'Gemini', or 'external model'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Gemini CLI specifically with distinct triggers around large context windows (>200k) and specific use cases. Unlikely to conflict with other code review or analysis skills due to the external tool and context size specificity. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent concrete guidance and clear workflows. The main weakness is verbosity - the critical warning about background mode is repeated multiple times, and the content could be more concise. The skill would benefit from consolidating redundant warnings and potentially splitting detailed reference material into separate files.
Suggestions
Consolidate the background/yolo warning into a single prominent section rather than repeating it in multiple places (When to Use, Running a Task, Quick Reference, Common Use Cases)
Consider moving the detailed troubleshooting section and model comparison table to separate reference files, keeping only essential quick-reference info in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful information but is verbose in places, with some repetition (the background/yolo warning appears multiple times in different sections). The model selection guide and quick reference table are efficient, but the troubleshooting section could be condensed. | 2 / 3 |
Actionability | Provides fully executable bash commands throughout, with specific flags, model names, and copy-paste ready examples. The quick reference table and common use cases sections give concrete, immediately usable commands. | 3 / 3 |
Workflow Clarity | Clear numbered steps for running tasks, explicit validation checkpoints (checking for hung processes, verifying cleanup), and well-defined decision points for model and approval mode selection. The troubleshooting section provides a clear detection -> diagnosis -> resolution workflow. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but everything is in a single file. The skill is quite long (~200 lines) and could benefit from splitting detailed troubleshooting or model comparison into separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- softaworks/agent-toolkit
- Commit
3027f20
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.