Gemini app replacing Gems with skills in November

Abner Li· Sep 27, 2026 · 5:26 PM UTC ·2 min read · 0 reactions · 0 comments · 6 views

More from 9to5Google tech Compare coverage Trending Talk Blindspots Daily Sources Live wire

TL;DR · WeSearch summary

Google is replacing its custom Gems feature with a new system called skills starting November 17, 2026. This migration will automatically convert existing Gems into skills, which serve a similar purpose by allowing users to provide custom instructions to Gemini. The new skills feature offers improved usability by enabling invocation via a slash command in the prompt box and allowing multiple skills to be used simultaneously.

Key facts

▪Google announced that Gems will be automatically migrated to skills on November 17, 2026.
▪Skills were introduced with Gemini Spark and allow users to give Gemini custom instructions similar to Gems.
▪Unlike Gems, skills can be invoked using a slash in the prompt box and multiple skills can be active at once.
▪Gems currently offer additional features like setting default tools and sharing via links, which may differ from the new skills implementation.
▪Google AI Pro and AI Ultra subscribers can create skills by switching to the Gemini Spark tab.

About this source

9to5Google files mainly under tech. We currently carry 542 of its stories.

All 9to5Google coverage →

Original article

9to5Google · Abner Li

Read full at 9to5Google →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	9to5Google
Canonical URL	https://9to5google.com/2026/09/27/gemini-gems-skills/
Publication time	Sun, 27 Sep 2026 17:26:40 +0000
Retrieval time	2026-09-27T19:46:40.048Z
Last seen	2026-09-27T19:46:40.048Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	nWKNTK7X-2pg · 1 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

// Make sure that nineto5ads exists, it will load ad once google tag exists window.nineto5ads = window.nineto5ads|| []; if (typeof adSizes === 'undefined') { var adSizes = {"leaderboard":{"mobile":[[320,50],[320,100]],"tablet":[[728,90],[320,100]],"desktop":[[970,250],[728,90],[970,70],[970,90]]},"sidebar":{"mobile":[300,250],"desktop":[[300,600],[300,250]]}}; } function getLeaderboardApstagSlotsSizes() { if ( window.innerWidth < 768 ) { return adSizes.leaderboard.mobile; } else if ( window.innerWidth < 1024 ) { return adSizes.leaderboard.tablet; } else { return adSizes.leaderboard.desktop; } } window.nineto5ads.push(function() { apstag.fetchBids({ slots: [{ slotID: "div-gpt-ad-1436850350386-0", slotName: "\/1049447\/9to5google-Top", sizes: getLeaderboardApstagSlotsSizes() }], timeout:…

Excerpt limited to ~120 words for fair-use compliance. The full article is at 9to5Google.

Anonymous · no account needed

Discussion

0 comments