gemini

Engineering Community

Skill notes

Step 1: Read the Experience Log

Before doing anything else, read the experience log: The log contains: [AUTO_APPROVE] entries — task types to always send to Gemini, no prompt needed [AVOID] entries — task types where Gemini underperformed, handle with Claude instead

Strong Gemini signals (+2 each)

Files involved are likely >50KB total (codebase scan, large logs, big documents) Task is purely read/analysis — no file editing needed Task matches an [AUTO_APPROVE] pattern in experience.md User explicitly says "use gemini", "ask gemini", "let gemini handle"

Mild Gemini signals (+1 each)

Multiple files need to be read and cross-referenced Task involves summarization or extraction from long content Token conservation would meaningfully benefit the conversation

Disqualifiers (skip Gemini entirely)

Task matches an [AVOID] pattern in experience.md → handle with Claude, mention why Task requires writing or editing files Task requires iterative tool-use loops Task is short and simple

Score >= 2 AND matches an [AUTOAPPROVE] pattern:

→ Go straight to Gemini — skip the question → Briefly note: "Routing to Gemini (auto-approved: [pattern name])"

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview gemini.preview
# Step 6: Post-Result Dissatisfaction Detection

Question: "Should I mark this task type as a poor fit for Gemini and handle it with Claude going forward?"
   Options:
     - "Yes, log it" — description: "Record this as an [AVOID] pattern"
     - "No, just this once" — description: "Don't log anything"

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.