CtrlK
BlogDocsLog inGet started
Tessl Logo

ask-gemini

Deprecated compatibility shim for Gemini advisor requests

58

Quality

66%

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/ask-gemini/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

The content is a tight, actionable deprecation notice that points users at the canonical workflow with copy-paste commands. Its only weakness is a mildly over-explained rationale sentence.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the rationale sentence ("This file exists only to preserve the public/catalog-visible...") is a minor instance of over-explanation that could be trimmed.

4 / 5

Actionability

It gives copy-paste-ready commands (`$ask gemini <question>` and `omx ask gemini "<question>"`) covering the common cases, matching the fully-executable anchor.

5 / 5

Workflow Clarity

As a single-purpose deprecation shim, the one action is unambiguous (do not invoke; use the alternative commands), qualifying for the simple-skill exception.

5 / 5

Progressive Disclosure

Under 50 lines, single purpose, no external references needed; the short heading-organized body satisfies the simple-skill progressive-disclosure exception.

5 / 5

Total

19

/

20

Passed

Description

41%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.

The description is honest about being a deprecated shim and identifies its niche, but it omits trigger guidance and concrete actions. As a catalog-visible compatibility contract it is acceptable yet thin.

Suggestions

Add a concrete action verb (e.g., "Forwards Gemini advisor requests to the canonical $ask workflow") to lift specificity.

Include the natural trigger phrase "ask gemini" so users searching for that term match this skill.

Optionally add a short "Use only to preserve the legacy ask-gemini contract" clause to make the "when" explicit.

DimensionReasoningScore

Specificity

"Deprecated compatibility shim for Gemini advisor requests" names the domain and a role ("shim") but lists no concrete actions, matching the anchor that names the domain with minimal/generic actions.

2 / 5

Completeness

The "what" (a compatibility shim for Gemini advisor requests) is clear, but there is no "Use when..." trigger clause, so completeness is capped at 3 per the guidelines.

3 / 5

Trigger Term Quality

"Gemini" and "advisor requests" are present, but the natural phrase a user would say ("ask gemini") is omitted; only one or two generic keywords appear.

2 / 5

Distinctiveness Conflict Risk

"Gemini advisor requests" carves a clear niche; minor overlap risk exists only with closely related general "ask" skills, fitting the mostly-distinct anchor.

4 / 5

Total

11

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Yeachan-Heo/oh-my-codex
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.