gemini
Gemini CLI for one-shot Q&A, summaries, and generation.
71
58%
Does it follow best practices?
Impact
99%
1.32xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gemini/SKILL.mdQuality
Discovery
32%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 identifies the tool (Gemini CLI) and broadly categorizes its use cases, but lacks concrete specificity about what actions it performs, misses a 'Use when...' clause entirely, and uses overly generic capability terms that could conflict with other skills. It needs explicit trigger guidance and more specific action descriptions to be effective for skill selection.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when the user wants to run a one-shot Gemini query from the command line' or 'when the user mentions gemini, gemini-cli, or wants to use Google's LLM for quick tasks'.
Replace vague terms like 'generation' with specific actions such as 'generate code snippets, rewrite text, answer factual questions, or summarize documents using Gemini CLI'.
Include natural user keywords and file types/contexts, e.g., 'gemini query', 'ask gemini', 'command-line LLM', to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the tool (Gemini CLI) and some actions (Q&A, summaries, generation), but these actions are broad and not very concrete—'generation' is vague, and there's no detail about what kinds of Q&A or summaries. | 2 / 3 |
Completeness | Describes a rough 'what' (Q&A, summaries, generation via Gemini CLI) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is weak enough to warrant a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Gemini CLI' and 'one-shot' which are somewhat relevant keywords, but misses natural user terms like 'ask gemini', 'gemini query', 'LLM', 'AI generation', or specific file/task triggers users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | 'Gemini CLI' is a distinct tool reference which helps, but 'Q&A, summaries, and generation' are extremely broad capabilities that could overlap with many other LLM-related or text-processing skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-structured skill that efficiently teaches one-shot Gemini CLI usage. Its main weakness is incomplete actionability—it could benefit from listing available model names and showing a concrete example with expected output. The safety note about --yolo and the auth guidance are good practical additions.
Suggestions
Add an example showing a complete invocation with expected output (e.g., `gemini --output-format json "List 3 colors"` → expected JSON response)
Include at least one or two common model names for the `--model` flag to make that command fully actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. Every line provides actionable information without explaining what Gemini is or how CLIs work. No unnecessary padding. | 3 / 3 |
Actionability | Provides concrete commands that are copy-paste ready, but lacks specifics like available model names, what JSON output format looks like, or what extension commands are available. The guidance is real but incomplete. | 2 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (one-shot CLI usage). The single action is unambiguous, and the auth note provides a clear fallback path. No multi-step destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with no need for external references, the content is well-organized into logical sections (quick start, extensions, notes). No bundle files are needed for this scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- Hung-Reo/hungreo-openclaw
- Commit
d8d7f4b
- 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.