feat(skills): add integrate-gemini skill - #37
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
fuller
force-pushed
the
feat/integrate-gemini-skill
branch
3 times, most recently
from
August 14, 2026 04:13
734d147 to
356bbfb
Compare
fuller
changed the title
fuller
force-pushed
the
feat/integrate-gemini-skill
branch
from
August 14, 2026 04:28
356bbfb to
c064eeb
Compare
fuller
marked this pull request as ready for review
August 14, 2026 04:30
mars-steven
previously requested changes
Aug 14, 2026
fuller
force-pushed
the
feat/integrate-gemini-skill
branch
from
August 18, 2026 04:45
c064eeb to
46090f5
Compare
…ration
- Add skills/integrate-gemini/{SKILL.md,reference.md,eval.mjs} covering
REST, the modern wss://ws.gemini.com WebSocket API, FIX 4.4, Prediction
Markets, and MCP server setup. Register it in skills/README.md.
- Documentation routing points at the live developer.gemini.com/api-reference
and the OpenAPI/AsyncAPI spec catalog rather than guessed .md page paths —
verified live, since category/landing pages and OpenAPI-driven leaf pages
render as empty component shells rather than usable content.
- Every WebSocket (order.place, order.cancel, orders@account, SUBSCRIBE) and
REST (/v1/order/new, /v1/order/cancel, /v1/balances,
/v1/prediction-markets/order) example is field-checked against the live
specs, including Master API key `account` routing that /v1/balances
requires.
- eval.mjs (15 checks) guards frontmatter, canonical endpoints, HMAC
signing, WebSocket envelope shapes, and a regression check for
fabricated local file paths.
- Fix a repo-wide stale reference: docs.gemini.com now redirects to
developer.gemini.com; updated across READMEs and
scripts/generate-sdks.sh.
fuller
force-pushed
the
feat/integrate-gemini-skill
branch
from
August 18, 2026 13:18
46090f5 to
33e96ea
Compare
mars-steven
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
integrate-gemini, a Claude Code skill for building Gemini REST, WebSocket, Prediction Markets, and FIX 4.4 integrations.Why
Existing Gemini skills predate the modern unified
wss://ws.gemini.comWebSocket API, FIX 4.4, and Prediction Markets contracts, and don't cover Master API key account routing or the MCP server. Agents integrating against Gemini today either guess at endpoint shapes or work from stale docs.What's different from main
skills/integrate-gemini/{SKILL.md,reference.md,eval.mjs}and registers it inskills/README.md.developer.gemini.com/api-referenceand the OpenAPI/AsyncAPI spec catalog rather than guessed.mdpage paths. Verified live:developer.gemini.comserves every path as.mdper itsllms.txt, but category/landing pages (rest-api/rest-api.md,docs/docs.md, etc.) and OpenAPI-driven leaf pages render as empty component shells rather than usable content — the skill now routes around both.order.place,order.cancel,orders@account,SUBSCRIBE) and REST (/v1/order/new,/v1/order/cancel,/v1/balances,/v1/prediction-markets/order) example is field-checked against the live specs, including a fix for Master API keyaccountrouting that the original examples missed (/v1/balancesmarks it hard-required).eval.mjs(15 checks) guards the frontmatter, canonical endpoints, HMAC signing, WebSocket envelope shapes, and a regression check for a fabricated localapis/path this review caught.docs.gemini.comnow 301-redirects todeveloper.gemini.com— updated across READMEs andscripts/generate-sdks.sh.gemini-developer(the existing skill) has overlapping trigger phrases with this one and is now behind it (no FIX, no Prediction Markets, references the pre-redirect domain). Left untouched here — separate follow-up.