gemini
Gemini CLI for one-shot Q&A, summaries, and generation.
51
58%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 are vague and generic. The description needs concrete actions, explicit trigger conditions, and more natural user-facing keywords.
Suggestions
Add a 'Use when...' clause specifying trigger conditions, e.g., 'Use when the user asks to run Gemini CLI, query Gemini from the command line, or needs a one-shot LLM response without a conversation.'
Replace vague terms like 'generation' with specific actions, e.g., 'generate code snippets, draft text, translate content via Gemini CLI'.
Include natural keywords users might say, such as 'gemini', 'google AI', 'command line AI', 'one-shot prompt', or 'gemini query'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the tool (Gemini CLI) and lists some actions (Q&A, summaries, generation), but these actions are broad and not very concrete — 'generation' is vague, and there's no detail on 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 for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores 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 skills involving text generation or summarization. | 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—the model name placeholder and sparse extension command details leave some gaps. The safety note about --yolo and the auth recovery instruction are good additions.
Suggestions
Provide at least one or two concrete model names for the --model flag (e.g., `gemini --model gemini-2.5-pro "Prompt..."`) to make the example fully actionable.
List the most common extension subcommands (e.g., `gemini extensions install`, `gemini extensions remove`) rather than just referencing `<command>`.
| 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 detail on available models (--model <name> is a placeholder), output format options, and what extensions 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 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.