translation-engine-spec

Define translation engine contracts, authentication, and error mapping for DeepL, Google Translate, and Google Cloud Translation.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Aliisa-yt/twitchbot --skill translation-engine-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translation-engine-spec
Source: https://github.com/Aliisa-yt/twitchbot/tree/main/.github/skills/translation-engine-spec
Command: npx skills add https://github.com/Aliisa-yt/twitchbot --skill translation-engine-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized contract and implementation guide for integrating various translation engines, ensuring consistent behavior, authentication, and error handling across different services.

Core Features & Use Cases

  • Engine Specification: Defines interfaces and attributes for translation engines like DeepL, Google Translate, and Google Cloud Translation.
  • Authentication & Quotas: Details how each engine handles API keys, OAuth, and rate limits.
  • Exception Handling: Maps engine-specific errors to a unified set of exceptions for robust error management.
  • Use Case: When developing a new translation feature, developers can consult this Skill to understand the exact requirements for adding a new translation provider, ensuring it integrates seamlessly with the existing TransManager.

Quick Start

Consult the translation-engine-spec skill for guidelines on implementing a new translation engine.

Frequently Asked Questions about translation-engine-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize API integration for multiple translation engines?

Standardize translation engine integration by defining a unified contract for interfaces, authentication, and exception handling across services like DeepL and Google Translate. This ensures consistent API implementation and seamless integration with the TransManager.

How does error handling work across different translation APIs?

Error handling maps engine-specific API errors to a unified set of exceptions for robust management. This standardizes diverse translation service errors into a consistent format, ensuring reliable error handling across implementations.

What is the best way to manage authentication and rate limits for translation services?

Manage authentication and rate limits by specifying how each translation engine handles API keys, OAuth, and quotas. The specification defines integration points with the TransManager to enforce rate limiting and ensure service availability.

Does the translation engine specification support DeepL and Google Cloud Translation?

The specification supports DeepL, Google Translate, and Google Cloud Translation. It defines specific engine attributes, authentication methods, and language code normalization for each supported translation service.

How do I add a new translation provider to the TransManager?

Add a new translation provider by consulting the specification to understand exact requirements for engine attributes and language code normalization. This ensures the new provider integrates seamlessly with the existing TransManager and rate limiting.