narova-google

Narova + Google (Gemini TTS and Veo)

Use this skill as an optional external speech and video-generation provider for Narova. Keep every Google API detail in this companion and communicate through the generic narova-tts-provider/v1 and narova-video-provider/v1 JSONL protocols. Let Narova own staging, provenance, generation recipes, the asset registry, caching, and rendering.

Requires the standalone Narova CLI, the Narova skill, Python 3.10+, network access, a Google AI Studio account with Gemini API access, and GEMINI_API_KEY.

Setup

1. Install the standalone Narova CLI as described by the narova skill, then install narova and narova-google as independently selected skills from ammar-hasan/narova.
2. Locate this installed skill from the directory containing this SKILL.md; call it <narova-google-skill-dir>.
3. Verify the workers:

bash <narova-google-skill-dir>/tool/setup.sh

1. Set the key only in the environment that runs Narova:

   export GEMINI_API_KEY="..."
   

2. Explicitly register one or both providers and verify:

   narova providers add \
     <narova-google-skill-dir>/tool/provider.json
   narova providers add \
     <narova-google-skill-dir>/tool/video-provider.json
   narova providers doctor google
   narova providers doctor veo
   

Installing this skill registers neither provider by itself. Unregistering a provider does not remove the skill.

Read references/configuration.md before use. It documents option mapping, errors, security, billing, AI-generation and SynthID disclosure, and removal.

Operating rules

• Treat synthesis and generation as explicit, billed network operations. The authored text/prompt is sent to Google.
• Keep GEMINI_API_KEY only in the process environment or a user-managed secret store; never put it in reel.config.mjs.
• Do not add a Google SDK to Narova or modify Narova's setup. These workers use the Python standard library.
• Do not copy these workers into the Narova skill. Registration composes two independently installed skills.
• Do not automatically retry a failed request. A lost response may still have been processed and billed.
• Let Narova publish synthesized audio or generated clips only after worker success; worker failures leave assets and the registry unchanged.
• Disclose that speech output is AI-generated and that generated videos may be SynthID-watermarked where that matters to the audience.