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 is too terse and lacks explicit trigger guidance ('Use when...'), making it difficult for Claude to know when to select this skill over others. While 'Gemini CLI' provides some distinctiveness, the listed capabilities (Q&A, summaries, generation) are generic and could apply to many tools. The description needs both more specific actions and clear selection criteria.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to run Gemini CLI, invoke Google's Gemini model from the command line, or needs one-shot text generation via gemini.'
Make the capabilities more concrete, e.g., 'Runs Gemini CLI commands to perform one-shot queries, summarize files or text, and generate content without maintaining a conversation session.'
Include natural trigger terms users might say, such as 'gemini', 'google gemini', 'gemini command', 'ask gemini', or 'gemini prompt'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gemini CLI) and some actions (Q&A, summaries, generation), but these actions are fairly generic and not deeply specific—'generation' is vague, and it doesn't describe concrete operations like 'run Gemini CLI commands' or 'pipe input to Gemini for summarization'. | 2 / 3 |
Completeness | It partially answers 'what does this do' but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also weak, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Gemini CLI' which is a relevant keyword, and 'Q&A', 'summaries', 'generation' are somewhat natural terms. However, it misses common variations like 'gemini', 'ask gemini', 'LLM', 'AI assistant', 'one-shot prompt', or 'command line' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Gemini CLI' is a fairly distinct trigger that narrows the domain, but 'Q&A, summaries, and generation' are extremely broad and could overlap with many other skills that handle text generation, summarization, or question answering. | 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 communicates how to use Gemini CLI in one-shot mode. Its main weakness is incomplete actionability—it could benefit from specifying available model names or showing a concrete example with expected output. Overall it's a solid simple skill that respects token budget.
Suggestions
Add one or two concrete model name examples (e.g., `gemini --model gemini-2.5-pro "Prompt..."`) to improve actionability.
Include a brief example showing expected output for at least one command (e.g., the JSON output format) to make guidance more concrete.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Gemini is or how CLIs work. Every line provides actionable information Claude wouldn't inherently know. | 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 recovery path. No multi-step destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (quick start, extensions, notes). No unnecessary nesting or monolithic walls of text. | 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
e893157
- 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.