Agent skill

Insurance Claims Orchestrator

by CALLE-AI in CALLE-AI/awesome-phone-call-agents

Orchestrate a two-call consent-first insurance claims intake sequence with CALL-E.

MITAuto-check passed

Install Insurance Claims Orchestrator

skills CLI
$ npx skills add CALLE-AI/awesome-phone-call-agents --skill insurance-claims-orchestrator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install CALLE-AI/awesome-phone-call-agents insurance-claims-orchestrator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/insurance-claims-orchestrator .claude/skills/insurance-claims-orchestrator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
insurance-claims-orchestrator
GitHub stars
107
Token cost
~1.3k tokens
SKILL.md length
517 words
Files
10 (incl. scripts, references, assets)
Skills in repo
101
Repo updated
First seen
Licence
MIT

At a glance

Orchestrate a two-call consent-first insurance claims intake sequence with CALL-E.

  • SKILL.md covers When To Use, When Not To Use, Required Inputs and Calls, plus 5 more sections
  • Runs TypeScript scripts from its folder; calls npm and npx; needs CALLE_API_KEY

What it does

Insurance Claims Orchestrator is an agent skill from CALLE-AI/awesome-phone-call-agents. Orchestrate a two-call consent-first insurance claims intake sequence with CALL-E. Call 1 collects a structured loss report from the policyholder. Call 2 verifies coverage using Call 1 results. Ambiguous outcomes route to human review. Introduces the first state-passing multi-call pattern in the repo.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts, reference files and assets (for example `assets/sequence-diagram.md`, `references/examples.md` and `references/safety.md`).

The repository describes itself as: Portable phone-call Agent Skills, apps, examples, adapters, and scheduler recipes for AI agents. The licence is MIT.

Example prompts

  • “/insurance-claims-orchestrator”

Requirements

  • Node.js
  • A credential in CALLE_API_KEY

What it can do on your machine

Read from SKILL.md and the folder at commit 38d4118. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • npm
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • CALLE_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Insurance Claims Orchestrator loads about 1.3k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 517 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from CALLE-AI/awesome-phone-call-agents at commit 38d4118, republished under its MIT licence (© CALLE-AI). 517 words, ~1,279 tokens.

Download SKILL.mdSave it as .claude/skills/insurance-claims-orchestrator/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
insurance-claims-orchestrator
description
Orchestrate a two-call consent-first insurance claims intake sequence with CALL-E. Call 1 collects a structured loss report from the policyholder. Call 2 verifies coverage using Call 1 results. Ambiguous outcomes route to human review. Introduces the first state-passing multi-call pattern in the repo.
license
MIT

insurance-claims-orchestrator

Use this skill when an agent needs to initiate an insurance claim intake on behalf of a policyholder using two sequential CALL-E calls, where the structured result of Call 1 directly gates and informs Call 2.

This skill does not approve or deny claims, quote settlement amounts, or make commitments on behalf of the insurer. It gathers structured evidence and routes to a human adjuster.

When To Use

  • Initiate an insurance claim on behalf of a policyholder who has consented to automated contact
  • Run a structured two-call sequence where results of Call 1 gate Call 2
  • Return machine-readable claim intake data to a downstream adjuster or CRM system
  • Demonstrate the state-passing multi-call pattern for other builders to copy

When Not To Use

  • Do not use to approve or deny claims
  • Do not use to collect payment, SSN, or banking information
  • Do not use when the policyholder has not explicitly consented to automated contact
  • Do not use outside 8:00 AM to 9:00 PM recipient local time
  • Do not use for collections, marketing, or unsolicited outreach

Required Inputs

  • phone: E.164 phone number of the policyholder, explicitly authorized
  • insurer_name: display name disclosed on the call
  • consent: must be true

Optional (live mode only):

  • CALLE_API_KEY: environment variable, required only for --live execution

Calls

Call 1 — Loss Report

Contacts the policyholder to collect:

  • Incident description (claimant's own words)
  • Incident date (ISO 8601)
  • Estimated damage in dollars (or null if declined)
  • Policy number confirmation

Exit gates — Call 2 is blocked if:

  • outcome is anything other than "completed"
  • policy_number_confirmed is null
  • Both incident_description AND incident_date are null

Any blocked gate routes to human review, not Call 2.

Call 2 — Coverage Verification

Uses Call 1 results to confirm:

  • Policy number (read back by claimant)
  • Policy active status
  • Coverage type applicability
  • Prior claims in the last 12 months
  • Adjuster follow-up timeline
Show full SKILL.md (214 more words)Show less

How to Run

Dry-run (no calls, no API key needed):

bash
cd apps/typescript/insurance-claims-orchestrator
npm install
npm run dry-run

Validate result fixtures against schema:

bash
npm run validate-schema

Live (requires CALLE_API_KEY):

bash
export CALLE_API_KEY=your_key_here
npx tsx src/index.ts --phone +1XXXXXXXXXX --live

Result Schemas

Both calls return structured JSON validated against references/schema.json.

Call 1 — LossReportResult:

FieldTypeNotes
outcomeenumcompleted / voicemail / no_answer / refused / unclear
incident_descriptionstring or nullClaimant's own words
incident_datestring or nullISO 8601 or null
estimated_damagenumber or nullDollar value or null
policy_number_confirmedstring or nullAs spoken by claimant

Call 2 — CoverageVerifyResult:

FieldTypeNotes
outcomeenumcompleted / voicemail / no_answer / refused / unclear
policy_activeboolean or nullNull if not established
coverage_verifiedenumyes / no / unknown — never guessed
prior_claims_12moboolean or nullNull if declined
adjuster_notifiedbooleanWhether adjuster follow-up was communicated
claimant_questionsstring or nullVerbatim unanswered questions

Safety Contract

See references/safety.md. Key rules:

  • AI disclosure is mandatory at the start of both calls
  • SSN, credit card, bank account, and password fields are never requested
  • Coverage decisions are never made or implied on the call
  • Ambiguous outcomes route to human review — never auto-retry unclear results
  • Phone numbers masked in all logs: first 4 chars + asterisks
  • Dry-run is the default — --live flag required for real calls

Idempotency

Each call execution is keyed by sha256(phone + step_id + incident_date). Re-running with the same inputs within 24 hours is a no-op, not a second call.

Files

skills/insurance-claims-orchestrator/
├── SKILL.md                    <- This file
├── references/
│   ├── safety.md               <- Safety contract and fail-closed dispositions
│   ├── schema.json             <- JSON Schema for both result shapes
│   └── two-call-pattern.md    <- Pattern guide for other builders
├── scripts/
│   ├── dry-run.ts              <- Fixture-based demo (no calls placed)
│   ├── validate-schema.ts      <- Validates result JSON against schema
│   └── fixtures/
│       ├── loss-report-result.json
│       └── coverage-verify-result.json
└── assets/
    └── sequence-diagram.md     <- Mermaid call flow diagram

© CALLE-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts, references, assets) in skills/insurance-claims-orchestrator of CALLE-AI/awesome-phone-call-agents.

  • SKILL.md
  • assets/sequence-diagram.md
  • references/examples.md
  • references/safety.md
  • references/schema.json
  • references/two-call-pattern.md
  • scripts/dry-run.ts
  • scripts/fixtures/coverage-verify-result.json
  • scripts/fixtures/loss-report-result.json
  • scripts/validate-schema.ts

Open the folder on GitHubat commit 38d4118

Compare with similar skills

Insurance Claims Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Insurance Claims Orchestrator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Insurance Claims Orchestrator this skillCALLE-AI/awesome-phone-call-agents107—~1.3kAutomated safety check: PassMIT
Insurance Claimmohitagw15856/pm-claude-skills1.4k—~1.1kAutomated safety check: PassMIT
Claimsruvnet/ruflo74k1 repos~1.1kAutomated safety check: PassMIT
Team Agent Orchestrationaffaan-m/ECC277k1 repos~1.2kAutomated safety check: PassMIT
Orca Orchestrationstablyai/orca89k—~916Automated safety check: PassMIT
Agent Orchestrator Taskruvnet/ruflo74k2 repos~1kAutomated safety check: PassMIT

Similar skills

  • Insurance Claim

    mohitagw15856/pm-claude-skills

    Write a clear insurance claim letter or appeal that supports a payout.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Claims

    ruvnet/ruflo

    Claims-based authorization for agents and operations. An agent skill from ruvnet/ruflo.

    74k GitHub starsUsed in 1 repo~1.1k tokens
    Backend & APIsAuto-check passed
  • Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.

    277k GitHub starsUsed in 1 repo~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Orca Orchestration

    stablyai/orca

    Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator…

    89k GitHub stars~916 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Agent skill for orchestrator-task - invoke with $agent-orchestrator-task

    74k GitHub starsUsed in 2 repos~1k tokens
    Agent WorkflowsAuto-check passed
  • Insurance Claim Appeal

    mohitagw15856/pm-claude-skills

    Appeal a denied insurance claim — read the real reason for the denial, find the strongest grounds, and draft the appeal with the evidence that answers it.

    1.4k GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

More from CALLE-AI/awesome-phone-call-agents

All 101 skills in this repo
  • Accessible Outing Verifier

    CALLE-AI/awesome-phone-call-agents

    Demonstrates advisory accessibility-planning checks with offline fixtures and a proposed bounded CALL-E workflow; use for exploring unknown or qualified venue claims without making calls.

    107 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Ground Truth Gate

    CALLE-AI/awesome-phone-call-agents

    A skill your agent uses when an agent holds some evidence for a physical-world claim but the evidence is broader, narrower, or older than the exact question asked, and it must first decide whether a…

    107 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed
  • Is It Accessible

    CALLE-AI/awesome-phone-call-agents

    Call a venue and ask the accessibility questions that matter to one specific person — step-free entry, hearing loop, guide dogs, quiet hours, changing places — then return a per-need verdict backed…

    107 GitHub stars~4.3k tokensUpdated yesterday
    Auto-check passed
  • Landmark Navigation Assist

    CALLE-AI/awesome-phone-call-agents

    Turns a pre-written, building-level location config into a CALL-E outbound phone-call task that guides a delivery driver through the last few hundred metres to a specific building using landmarks…

    107 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Research Gap Call Verifier

    CALLE-AI/awesome-phone-call-agents

    Turn cited business research into a bounded, approval-gated phone-call plan that asks only unresolved factual questions, then reconcile CALL-E-compatible results without treating voicemail, refusal…

    107 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Structured Outcome Followup Call

    CALLE-AI/awesome-phone-call-agents

    Place a goal-driven CALL-E call that collects specific structured answers, score those answers against a deterministic rubric you supply, and conditionally trigger a follow-up action — all runnable…

    107 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Questions about Insurance Claims Orchestrator

What does Insurance Claims Orchestrator do?

Orchestrate a two-call consent-first insurance claims intake sequence with CALL-E. Insurance Claims Orchestrator is an agent skill from CALLE-AI/awesome-phone-call-agents. Orchestrate a two-call consent-first insurance claims intake sequence with CALL-E.

How do I install Insurance Claims Orchestrator in Claude Code?

Run `npx skills add CALLE-AI/awesome-phone-call-agents --skill insurance-claims-orchestrator -a claude-code`. Or copy the skill folder (skills/insurance-claims-orchestrator in CALLE-AI/awesome-phone-call-agents) into .claude/skills/insurance-claims-orchestrator in your project. Claude Code loads it when a task matches its description.

How do I install Insurance Claims Orchestrator in Codex?

Run `npx skills add CALLE-AI/awesome-phone-call-agents --skill insurance-claims-orchestrator -a codex`. Or copy the skill folder (skills/insurance-claims-orchestrator in CALLE-AI/awesome-phone-call-agents) into .agents/skills/insurance-claims-orchestrator in your project. Codex loads it when a task matches its description.

Can I use Insurance Claims Orchestrator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CALLE-AI/awesome-phone-call-agents --skill insurance-claims-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/insurance-claims-orchestrator, .gemini/skills/insurance-claims-orchestrator, .github/skills/insurance-claims-orchestrator and .opencode/skills/insurance-claims-orchestrator in your project.

What does Insurance Claims Orchestrator need to run?

Going by SKILL.md and its folder, Insurance Claims Orchestrator needs TypeScript for the scripts in its folder, the command-line tools its instructions call (npm and npx) and credentials named CALLE_API_KEY. Our summary lists: Node.js; A credential in CALLE_API_KEY.

Does Insurance Claims Orchestrator access the network?

SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Insurance Claims Orchestrator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Insurance Claims Orchestrator use?

Insurance Claims Orchestrator is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Insurance Claims Orchestrator use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Insurance Claims Orchestrator?

Skills that share tags, products or a category with Insurance Claims Orchestrator: Insurance Claim (mohitagw15856/pm-claude-skills, 1.4k stars), Claims (ruvnet/ruflo, 74k stars), Team Agent Orchestration (affaan-m/ECC, 277k stars) and Orca Orchestration (stablyai/orca, 89k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Insurance Claims Orchestrator?

CALLE-AI (a GitHub organization) maintains it in CALLE-AI/awesome-phone-call-agents, which has 107 GitHub stars. The repository holds 101 skills in this directory. The repository was last updated on October 10, 2026.

Source: CALLE-AI/awesome-phone-call-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.