agentleFS
Sign inStart free
lza6lza6/claw-code-tingfeng/skills/ask-gemini/SKILL.md

ask-gemini

Skill5 starsChanged 12 days agoMITView on GitHub

Ask Gemini via local CLI and capture a reusable artifact

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the locally installed Gemini CLI as a direct external advisor for brainstorming, design feedback, and second opinions.

    line 8
  2. Distinctive:

    Run Gemini through the canonical OMX CLI command path (no MCP routing):

    line 19
  3. Distinctive:

    If needed, adapt to the user's installed Gemini CLI variant while keeping local execution as the default path.

    line 32
  4. Very specific:

    If gemini is not found, do not switch to MCP.

    line 37
  5. Distinctive:

    Ask the user to install/configure Gemini CLI.

    line 40
  6. Distinctive:

    After local execution, save a markdown artifact to:

    line 48

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ask Gemini (Local CLI)

Use the locally installed Gemini CLI as a direct external advisor for brainstorming, design feedback, and second opinions.

Usage

/ask-gemini <question or task>

Routing

Preferred: Local CLI execution

Run Gemini through the canonical OMX CLI command path (no MCP routing):

omx ask gemini "{{ARGUMENTS}}"

Exact non-interactive Gemini CLI command from gemini --help:

gemini -p "{{ARGUMENTS}}"
# equivalent: gemini --prompt "{{ARGUMENTS}}"

If needed, adapt to the user's installed Gemini CLI variant while keeping local execution as the default path.

Legacy compatibility entrypoints (./scripts/ask-gemini.sh, npm run ask:gemini -- ...) are transitional wrappers.

Missing binary behavior

If gemini is not found, do not switch to MCP. Instead:

  1. Explain that local Gemini CLI is required for this skill.
  2. Ask the user to install/configure Gemini CLI.
  3. Provide a quick verification command:
gemini --version

Artifact requirement

After local execution, save a markdown artifact to:

.omx/artifacts/gemini-<slug>-<timestamp>.md

Minimum artifact sections:

  1. Original user task
  2. Final prompt sent to Gemini CLI
  3. Gemini output (raw)
  4. Concise summary
  5. Action items / next steps

Task: {{ARGUMENTS}}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free