AI & information

Two skills demand different formats: resolve the conflict first

Choose one output contract before combining useful skills with incompatible headings, tables or file requirements.

Google’s October 21, 2026 announcement describes the Gemini Customize hub for managing skills and connected apps. It dates the gradual rollout to October 13, rather than announcing that every account gained access on October 21. As more saved instructions become available together, decide how conflicting format rules should work before using them. The same planning step helps with ChatGPT and Codex skills; it does not establish identical features across products.

Two useful skills can still disagree. One may demand a one-page briefing while another requires a detailed audit table. Applying both literally can produce a document that satisfies neither task.

Define one final deliverable

List the conflicting requirements before generating the file. Choose which skill governs the output format and which contributes a method or quality check. Explicit user requirements still matter; a skill cannot silently replace the requested deliverable.

For example, use a research skill to verify sources, then a briefing skill to produce one page. Keep the research checklist in working notes rather than appending an unwanted ten-page audit. If the user actually needs both files, name them separately.

Test the combination

Run a small input with one known source and one uncertain claim. Check that the final file follows the chosen format and still marks the uncertainty. If the environment cannot use both skills together, apply the stages explicitly instead of claiming that both ran.

Sources & further reading

  1. Google — Gemini Customize, published 21 October; rollout from 13 October
  2. OpenAI — Build skills
  3. OpenAI — Skills and plugins

Sources support the technical explanations. Examples and suggested checks are editorial guidance.