CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gemini-search

Search research papers via Gemini for broad literature discovery. Use when user says "gemini search", "gemini papers", "search with gemini", or wants AI-powered literature discovery beyond arXiv/Semantic Scholar indexes.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/gemini-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable skill with an excellent fallback-aware workflow, undermined by redundancy and monolithic structure. The model-override documentation and MCP setup instructions are duplicated, and one-time setup material plus the prompt template belong in reference files to slim the main body.

Suggestions

Move the Environment & Setup section (prerequisites, MCP configuration variants, authentication) into a references/SETUP.md file and keep a one-line pointer plus the verification command in SKILL.md, cutting ~70 lines from the always-loaded body.

Consolidate the model override documentation: the DEFAULT_MODEL bullet and the override blockquote list repeat the same options — keep one canonical table or list with the syntax, effect, and caveat per option.

Place the full search prompt template in a reference file (or a single canonical block) and make the CLI fallback reference it explicitly instead of "...same prompt as above...", and embed the timeout directly in the CLI command (e.g., timeout 120 gemini -p '...').

Trim the "When to use which" subsection and the three MCP setup variants (JSON, npx JSON, one-liner) down to the one-liner plus one config example, since the "MCP first, CLI second" rationale already appears in Key Rules.

DimensionReasoningScore

Conciseness

Operational specifics Claude would not know (MCP tool names, model routing quirks, stderr/timeout handling) earn their tokens, but there is noticeable redundancy: model overrides are documented twice (Constants bullet plus the blockquote list), three MCP setup variants are given, and "When to use which" repeats the "MCP first, CLI second" rule already in Key Rules.

3 / 5

Actionability

The full mcp__gemini-cli__ask-gemini call with a copy-paste prompt template, exact MCP JSON configs, npm install commands, and a CLI fallback command are highly executable; minor gaps include the CLI fallback eliding the prompt ("...same prompt as above...") and the 120s timeout being stated as prose rather than embedded in the command.

4 / 5

Workflow Clarity

Five clearly sequenced steps with explicit error-recovery loops (MCP failure falls back to CLI, then to alternative skills), a Verify Setup check, and degraded-output handling ("If Gemini returns fewer papers than requested, note this but do not re-query") match the explicit-validation-and-feedback-loops anchor; no destructive or batch cap applies.

5 / 5

Progressive Disclosure

Sections are well-headered and navigable, but roughly 70 lines of one-time setup/install/auth content and the long search prompt template are inlined in a ~225-line SKILL.md with no reference files, fitting the anchor where content that should be separate is inline.

3 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit, natural trigger list and a clearly stated purpose. Its main weaknesses are thin capability enumeration (one action plus a restated domain) and a trigger clause ("AI-powered literature discovery") that could collide with sibling literature-search skills.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("Search research papers via Gemini"), but "broad literature discovery" restates the domain rather than enumerating additional specific capabilities, matching the 1-2-concrete-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

Explicitly answers both what ("Search research papers via Gemini for broad literature discovery") and when ("Use when user says..." with concrete trigger phrases), matching the anchor requiring both clearly and explicitly with concrete triggers; the when-clause is maximally explicit so the 4-anchor caveat does not apply.

5 / 5

Trigger Term Quality

Includes natural quoted phrases users would actually say ("gemini search", "gemini papers", "search with gemini") plus "AI-powered literature discovery", but misses common variations such as "find papers", "literature review", or "search papers on".

4 / 5

Distinctiveness Conflict Risk

"via Gemini" and gemini-prefixed triggers carve a clear niche explicitly contrasted with arXiv/Semantic Scholar, but the broader "wants AI-powered literature discovery" clause overlaps closely related sibling search skills, posing minor overlap risk.

4 / 5

Total

16

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/gemini-search/SKILL.md

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.