extraction-policy-lookup-ar

Retrieve policy documents from Libra internal systems using identifiers.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/ossarg/ali --skill extraction-policy-lookup-ar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extraction-policy-lookup-ar
Source: https://github.com/ossarg/ali/tree/main/skills/extraction-policy-lookup-ar
Command: npx skills add https://github.com/ossarg/ali --skill extraction-policy-lookup-ar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This integration layer retrieves policy documents from Libra Seguros's internal systems using the available identifiers such as policy number, vehicle domain, insured or taker data, without performing any analysis on the policy content. The analysis is performed by extraction-policy-summary-ar on the document returned.

Core Features & Use Cases

  • Retrieve policy documents from internal systems using identifiers such as policy number, vehicle domain, insured or taker data.
  • Output a path to the recovered policy document for downstream processing, or null if not found, with diagnostic details.
  • Support prioritized search: policy number > vehicle domain > insured identifiers > combined insured name and vehicle details.

Quick Start

Command your AI to fetch the policy document from Libra's internal systems using the known identifiers.

Frequently Asked Questions about extraction-policy-lookup-ar

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

FAQPage Schema
How do I retrieve policy documents from internal insurance systems?

To retrieve policy documents from internal insurance systems, query the system using available identifiers such as policy number, vehicle domain, or insured data. It returns a file path to the document or null if not found.

What identifiers can I use to look up insurance policy data?

You can look up insurance policy data using policy number, vehicle domain, insured data, or taker data. The system applies a prioritized search workflow starting with the policy number and falling back to combined identifiers.

What happens when a policy lookup fails to find a matching document?

When a policy lookup fails to find a matching document, the system returns a null result along with diagnostic details. This standardized output structure ensures downstream processing can handle missing documents gracefully.

Can I analyze the content of a retrieved policy document directly during the lookup?

No, you cannot analyze policy content directly during the lookup. This integration strictly retrieves the document path and delegates analysis to the extraction-policy-summary-ar tool for separate processing.

How do I start fetching policy files from the Libra system using known identifiers?

To start fetching policy files from the Libra system, command your AI to retrieve the document using your known identifiers. The system prioritizes the search and outputs a path to the recovered policy document for downstream processing.