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 ./openclaw/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...'). While it names the tool (Gemini CLI) and hints at capabilities, the actions listed are broad and generic. It would be difficult for Claude to reliably distinguish this skill from other generation or summarization skills without clearer triggers and more specific capability descriptions.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to run a one-shot Gemini CLI command for quick answers, text summaries, or content generation from the terminal.'
Make capabilities more concrete by specifying what kinds of Q&A, summaries, or generation are supported, e.g., 'Runs gemini CLI commands to answer questions, summarize documents or text, and generate content in a single invocation without interactive mode.'
Include natural trigger terms users might say, such as 'gemini command line', 'ask gemini', 'gemini prompt', or 'gemini one-shot'.
| 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 kind of content or how. | 2 / 3 |
Completeness | Describes what it does at a high level 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 a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Gemini CLI' which is a useful trigger term, and 'Q&A', 'summaries', 'generation' are somewhat relevant, but misses natural user phrases like 'ask Gemini', 'gemini command line', 'one-shot prompt', or file type references. | 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 capabilities that could overlap with many other skills. The 'one-shot' qualifier helps somewhat. | 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 slightly incomplete actionability—specific model names and extension subcommands would make it more immediately useful. Overall it's a solid simple skill that respects token budget.
Suggestions
List common/available model names instead of just `<name>` placeholder (e.g., `gemini-2.5-pro`, `gemini-2.5-flash`)
Provide at least one concrete extension subcommand example (e.g., `gemini extensions install <name>`) rather than the generic `<command>` placeholder
| 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 detail on available models, output format options, or what extensions commands are available. The `--model <name>` placeholder without listing actual model names reduces actionability. | 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
- trpc-group/trpc-agent-go
- Commit
af8bd5f
- 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.