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 a 'Use when...' clause, making it difficult for Claude to know when to select this skill. While 'Gemini CLI' provides some distinctiveness, the listed capabilities (Q&A, summaries, generation) are generic and don't clearly differentiate this skill from other text generation or summarization tools.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to run Gemini CLI commands, ask Gemini a one-shot question, or generate summaries via the Gemini command-line tool.'
Be more specific about capabilities—what kind of Q&A, what kind of generation? E.g., 'Runs Google Gemini CLI to answer questions, summarize documents, and generate text without maintaining a conversation session.'
Include natural trigger terms users might say, such as 'gemini', 'ask gemini', 'gemini command line', 'one-shot prompt', or 'google gemini'.
| 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 there's no detail on what kind of content is generated or what Q&A entails. | 2 / 3 |
Completeness | It partially answers 'what does this do' but completely lacks any 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric should cap completeness at 2, and since the 'what' is also weak, a score of 1 is appropriate. | 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', 'one-shot', 'LLM', 'AI query', or 'command line' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Gemini CLI' is a fairly distinct identifier that narrows the domain, but 'Q&A, summaries, and generation' are extremely broad actions that could overlap with many other skills involving text generation or summarization tools. | 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 that it could be slightly more actionable by specifying available model names or common use-case examples. Overall it's a solid simple skill that respects token budget and is easy to follow.
Suggestions
Add 1-2 concrete examples showing real prompts with expected output patterns (e.g., summarization, code generation) to improve actionability.
Mention at least one or two common model names (e.g., `gemini-2.5-pro`) so Claude doesn't have to guess valid values for `--model`.
| 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 key details like available model names, what output formats are supported, what extension commands exist, and what specific use cases each flag serves. | 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) that are easy to scan. | 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
- attilaczudor/Test
- Commit
b4fc4af
- 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.