Notary Engine Optimizer (Internal)

Select Gemini models with JSON validation and retry fallbacks for EscriAR.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/diegogalmarini/EscriAR --skill notary-engine-optimizer-internal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Notary Engine Optimizer (Internal)
Source: https://github.com/diegogalmarini/EscriAR/tree/main/.agent/skills/notary-engine-optimizer
Command: npx skills add https://github.com/diegogalmarini/EscriAR --skill notary-engine-optimizer-internal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures the EscriAR system consistently uses the most powerful and accurate AI model available, preventing service outages due to unexpected changes in the Google Gemini API.

Core Features & Use Cases

  • Dynamic AI Model Selection: Automatically switches between different Gemini models (GOLD, SILVER, BRONZE) based on performance and availability.
  • Strict Data Validation: Enforces JSON output and requires source evidence for all extracted data to prevent hallucinations.
  • Self-Correction: Automatically retries failed extractions with error feedback to the AI.
  • Use Case: Guarantees that critical document analysis tasks within EscriAR always use the best available AI, ensuring data integrity and continuous operation even if one AI model experiences downtime or changes.

Quick Start

Use the Notary Engine Optimizer skill to ensure all AI extractions are validated and use the best available model.

Frequently Asked Questions about Notary Engine Optimizer (Internal)

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

FAQPage Schema
How do I prevent AI service disruptions when Google Gemini API changes occur?

To prevent AI service disruptions from Gemini API changes, implement a tiered model hierarchy with GOLD, SILVER, and BRONZE levels to automatically switch to available models and maintain continuous operation.

How do I enforce strict JSON output and prevent hallucinations in AI document extraction?

You can enforce strict JSON output and prevent hallucinations by implementing data validation rules that require source evidence for all extracted data, utilizing auto-correction retry mechanisms to fix failed extractions.

What is the best way to manage dynamic AI model selection based on performance and availability?

Dynamic AI model selection is best managed by categorizing models into a tiered hierarchy, allowing your system to automatically select the most powerful and accurate available model while preventing outages.

How do I automatically retry failed AI data extractions with error feedback?

Automatically retry failed AI data extractions by implementing a self-correction mechanism that feeds error feedback directly back to the AI, ensuring strict data validation and JSON enforcement on subsequent attempts.

Can I use tiered model hierarchy to ensure data integrity for critical document analysis?

Yes, using a tiered model hierarchy ensures data integrity for critical document analysis by dynamically routing requests to the best available AI model and enforcing strict source evidence requirements.

Why does my AI extraction fail when the primary Gemini model experiences downtime?

AI extractions fail during primary model downtime if there is no fallback mechanism; implementing a tiered model hierarchy with auto-correction retry mechanisms ensures continuous operation by switching to available models.