summarize_skill

Overview

This skill is a deprecated wrapper that routes calls to the newer synthesize tool for backward compatibility. It exists to avoid breaking legacy integrations while teams migrate to synthesize. New integrations should call synthesize directly.

How this skill works

When invoked, the skill forwards input and parameters to the synthesize tool and returns the synthesize response unchanged. It performs no transformation beyond routing and may emit a deprecation notice. Behavior, options, and output format mirror synthesize exactly.

When to use it

• Maintain compatibility for legacy scripts or automation that still call summarize
• Run tests that validate migration behavior between summarize and synthesize
• Support third-party integrations that cannot be updated immediately
• Short transitional periods during staged upgrades
• Do not choose summarize for new development

Best practices

• Migrate code and documentation to synthesize as soon as feasible
• Update CI and deployment pipelines to call synthesize directly
• Add logging or alerts when summarize is used to track legacy usage
• Treat summarize as a temporary bridge, not a feature-stable endpoint
• Pin dependency versions during migration to avoid unexpected behavior

Example use cases

• A legacy ETL job that still references summarize while the team updates pipelines
• A CI job that validates incoming requests are compatible with synthesize by routing through summarize
• A vendor integration that cannot be changed immediately and requires continued compatibility
• Short-term rollouts where parts of the system switch to synthesize gradually