Google Gemini Skills: Can You Combine Custom AI Instructions?

Learn how Google Gemini Skills handle combined custom AI instructions, including overlapping rules, setup limits and ways to keep outputs consistent day to day.

By ELYMENT Insights
Google Gemini Skills: Can You Combine Custom AI Instructions?

Yes. With Google Gemini Skills, you can combine reusable instructions in one task. Gemini can also apply active skills automatically when they fit the prompt. A Sydney property team could use one skill to check site notes and another to format an internal handover and a client draft. The workflow is most useful when both outputs preserve the same facts and approval status. Availability and connected-app access depend on the account and settings.

Consider a Sydney apartment flooring project where strata has approved the renovation, but the goods lift is still to be booked. The building manager has offered Thursday as a provisional slot. A site handover needs to say who will secure the booking. A client update needs to explain when the start date can be confirmed. Both documents should carry the same facts, even though they are written for different readers.

The difference matters before a crew or delivery vehicle is booked. The NSW Government’s strata renovation guidance explains how scheme by-laws and renovation approvals come into play. On a live project, the works approval and the building’s access arrangements belong in separate fields. A draft that collapses the two can make a provisional start look settled.

Give each skill one job

A Gemini skill saves instructions and, where supported, reference material for reuse across chats. Google’s Gemini Apps guidance says you can select multiple skills for the same task using the skill picker. Enter /, or @ if your version has the updated shortcut, and choose the relevant skills.

Gemini can also apply active skills automatically when it judges that they match the task. Selecting skills explicitly gives a team a repeatable starting point when testing a workflow.

Two example skills for a Sydney site handover

  • Example skill: Site facts
  • Reusable instructions: Record the source for each approval, access window and start date. Keep requested, provisional and confirmed statuses distinct. Flag gaps and conflicting records for review.
  • Expected result: A short fact list that marks Thursday’s lift slot as provisional and records the missing confirmation.
  • Example skill: Handover and client update
  • Reusable instructions: Use the fact list to draft an internal handover with action owners and a brief client update in plain Australian English. Carry the source statuses into both drafts.
  • Expected result: The coordinator sees who must confirm the lift booking. The client sees that the start date is pending confirmation.

With both skills selected, a prompt could read:

Use the supplied site notes to list confirmed facts, provisional details and items to verify. Draft an internal site handover and a client update from that list. Use the same status for each date in both drafts. Flag conflicting records for the coordinator and leave release of the client update to them.

The same fact-checking instructions could be reused in a supplier delivery brief without rebuilding the client template. For teams that need better inputs before they reach the reporting stage, Elyment’s guide to capturing access and site risks in flooring quote intake shows which details are worth recording early.

Test what happens when the records disagree

Run the same two skills against three sets of redacted notes: one with a confirmed booking, one with no booking and one with conflicting dates. Compare the generated drafts with the original notes. Check whether facts survive the change of audience and how much rewriting the coordinator still has to do.

Where one skill demands a firm date and the other permits provisional dates, revise the formatting instruction to preserve the status from the source record.

Google’s help notes that individually saved copies update independently of the shared original. Nominate one owner for the version the team uses.

Automatic selection determines which active instructions Gemini may apply. A recurring trigger and access to connected apps are configured separately. Keep the project register as the record of approvals, and assign a person to review any message that commits the business to a date, price or scope.

Elyment’s analysis of Google’s managed background agents explains the additional controls involved when a workflow goes beyond drafting.

Check where the team can use Skills

As at 20 November 2026, access to Skills and migration of existing Gems follow separate timetables.

  • Personal Google accounts
  • For users aged 18 and over, Google’s Gems transition guide dates the move to Skills and read-only Gems to 17 November 2026.
  • Google lists 17 December 2026 for removal of the old Gems from Gemini Apps.
  • Compare migrated skills with the originals before that date.
  • Unsupported file types may be omitted. If a Gem’s files total more than 100 MB, Google says it removes the largest files first until the remaining set fits.
  • Work and school accounts
  • Check availability in the intended account and product.
  • Google’s Workspace rollout notice gives 9 November 2026 for the start of Rapid Release and 30 November 2026 for Scheduled Release in eligible domains.
  • This rollout covers Skills inside Workspace apps and Workspace Studio.
  • Access there depends on the edition or add-on, administrator settings and the user being at least 18.
  • Google’s admin migration guidance sets later dates for existing Gems, with business and enterprise migration starting no sooner than March 2027 and Education no sooner than June 2027.
  • Skills created in the Gemini app are managed separately from Skills in Workspace apps.
  • References and tools
  • Google says Gemini app skills can work with Keep Activity off, while connected services such as Drive and Calendar are unavailable in that setting.
  • Recipients also need access to any files a shared skill relies on.
  • Google lists Canvas and Deep Research among the tools that currently lack Skills support.

Test with an approved account and redacted documents before using live client material. The OAIC’s guidance on commercial AI and privacy advises organisations to consider what personal information they enter and who can access it.

Confirm that each intended user can open the approved source files and that the combined drafts preserve the original facts.

Elyment’s Sydney AI workflow and systems services cover how teams can assess and implement this type of process.

Review a workflow your team repeats

Bring a site handover, client update or reporting process. Elyment can help map the source records, reusable instructions and approval steps for your Sydney property or project team.

Request a Workflow Review


Sources and references

  1. NSW Government – Strata renovations
  2. Google – Gemini Apps Skills guidance
  3. Elyment – AI flooring quotes and site risk intake
  4. Elyment – Google’s managed background agents
  5. Google – Gems transition guide
  6. Google Workspace – Skills rollout notice
  7. Google Workspace – Admin migration guidance
  8. OAIC – Privacy guidance on commercially available AI products
  9. Elyment – Sydney AI workflow and systems services
  10. Elyment – Contact


Review a workflow your team repeats

Bring a site handover, client update or reporting process. Elyment can help map the source records, reusable instructions and approval steps for your Sydney property or project team.

Review My Workflow

Explore more ELYMENT articles