New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Priority Call Waterfall

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

Fill one open opportunity by calling a priority-ordered candidate list with CALL-E, one candidate at a time, until someone accepts — waitlist backfill, shift coverage, on-call escalation, and…

MITAuto-check passedDevOps & Cloud

Install Priority Call Waterfall

skills CLI
$ npx skills add CALLE-AI/awesome-phone-call-agents --skill priority-call-waterfall -a claude-code

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

GitHub CLI
$ gh skill install CALLE-AI/awesome-phone-call-agents priority-call-waterfall --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/priority-call-waterfall .claude/skills/priority-call-waterfall && 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
priority-call-waterfall
GitHub stars
107
Token cost
~1.5k tokens
SKILL.md length
874 words
Files
5 (incl. scripts, references)
Skills in repo
101
Repo updated
First seen
Licence
MIT

At a glance

Fill one open opportunity by calling a priority-ordered candidate list with CALL-E, one candidate at a time, until someone accepts — waitlist backfill, shift coverage, on-call escalation, and…

  • Works in 8 steps: Confirm the user explicitly wants the… → Collect the waterfall fields → Ask for any missing required field. Do… → …
  • Tasks that involve Incident response
  • SKILL.md covers When To Use, When Not To Use, Core Workflow and Required Fields, plus 3 more sections
  • Runs JavaScript scripts from its folder

What it does

Priority Call Waterfall is an agent skill from CALLE-AI/awesome-phone-call-agents. Fill one open opportunity by calling a priority-ordered candidate list with CALL-E, one candidate at a time, until someone accepts — waitlist backfill, shift coverage, on-call escalation, and service dispatch workflows.

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

It sits in DevOps & Cloud, covering Incident response. The repository describes itself as: Portable phone-call Agent Skills, apps, examples, adapters, and scheduler recipes for AI agents. The licence is MIT.

When your agent uses it

  • Tasks that involve Incident response

Example prompts

  • “/priority-call-waterfall”

Requirements

  • Node.js

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the user explicitly wants the opening filled by phone now.
  2. Collect the waterfall fields
  3. Ask for any missing required field. Do not infer phone numbers or priorities.
  4. Validate the input with scripts/validate-waterfall-input.mjs when a structured
  5. Show the user a masked preview: the opening, the calling order, and the cap. Get
  6. Call candidates strictly one at a time, in priority order
  7. Stop conditions, checked after every call
  8. Report the outcome using the Output Format below.

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 1 file in scripts/ (JavaScript), which the agent can run.

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

  • Network

    No URLs in SKILL.md.

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Priority Call Waterfall loads about 1.5k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 874 words of instructions outside code blocks.

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

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). 874 words, ~1,549 tokens.

Download SKILL.mdSave it as .claude/skills/priority-call-waterfall/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
priority-call-waterfall
description
Fill one open opportunity by calling a priority-ordered candidate list with CALL-E, one candidate at a time, until someone accepts — waitlist backfill, shift coverage, on-call escalation, and service dispatch workflows.
license
MIT

Priority Call Waterfall

Use this skill when the user has one concrete opportunity (an open appointment slot, an uncovered shift, an unassigned job, an unacknowledged incident) and a priority-ordered list of candidates, and wants each candidate called in order until one accepts.

priority-call-waterfall is a calling-pattern skill. It does not add a CALL-E backend API, a queue service, or a daemon. It turns one authorized "fill this opening" request into a strictly sequential series of one-off CALL-E calls with a hard stop at the first acceptance.

When To Use

Use this skill for:

  • backfilling a freed appointment slot from a waitlist (a cancellation or no-show)
  • finding coverage for an open shift from a ranked list of staff
  • dispatching one job to the first available provider on a call-down list
  • escalating an incident through an on-call chain until someone acknowledges
  • any "call these people in order until one says yes" request with a single opening

When Not To Use

Do not use this skill to:

  • call multiple candidates in parallel or race candidates against each other
  • continue calling after a candidate has accepted
  • offer the same opening to more than one person at a time
  • broadcast announcements, promotions, or anything that is not a real single opening
  • build a recurring schedule (pair with a scheduler skill instead; each waterfall run is a one-shot workflow)
  • guess phone numbers, priorities, consent, or the opening's details
  • call third-party numbers unless the user states the candidates expect these calls (an existing waitlist, staff roster, or on-call rotation is that expectation)

Core Workflow

  1. Confirm the user explicitly wants the opening filled by phone now.
  2. Collect the waterfall fields:
    • the opening: what it is, when it is, and any details a candidate needs to decide
    • the candidate list: name, E.164 phone number, and priority (lower calls first)
    • an optional per-run call cap (default: call every listed candidate at most once)
    • an optional deadline after which the waterfall must stop even without an acceptance
  3. Ask for any missing required field. Do not infer phone numbers or priorities.
  4. Validate the input with scripts/validate-waterfall-input.mjs when a structured payload is available. Reject duplicate phone numbers and duplicate priorities.
  5. Show the user a masked preview: the opening, the calling order, and the cap. Get explicit confirmation before the first call.
  6. Call candidates strictly one at a time, in priority order:
    • build a goal that names the business or requester, the candidate, the opening, and asks for a clear yes or no (see references/goal-and-result.md)
    • request a structured result with a required accepted field (yes or no)
    • place exactly one CALL-E call and wait for its terminal status
    • treat an ambiguous provider outcome (voicemail, no answer, unclear answer, timeout, or failed call) as a halt condition; it must not automatically start another call or conflicting side effect.
    • only a clear 'no' counts as a decline that allows moving to the next candidate.
  7. Stop conditions, checked after every call:
    • a candidate accepted → record who, stop immediately, never call the rest
    • the list, cap, or deadline is exhausted → stop and report the opening unfilled
  8. Report the outcome using the Output Format below.

Use this shape per candidate:

text
build goal -> one call -> read structured result -> accept? stop : next candidate
Show full SKILL.md (345 more words)Show less

Required Fields

For each run, require:

  • opening — a short human-readable description of the single thing being offered
  • candidates[] — each with name, phone (E.164), and priority (unique integer; lower calls first)

Optional:

  • maxCalls — cap the number of candidates called this run
  • deadline — an instant after which no further calls may start
  • language / region — passed through to CALL-E when the user provides them

Phone numbers must be E.164. Mask phone numbers in user-facing summaries and reports.

Safety Rules

Read references/safety.md for the full safety contract.

Always follow these rules:

  • Every call is a real-world side effect; the user confirms the run before call one.
  • One opening, one acceptance: after a yes, the waterfall is over. Calling candidate N+1 after candidate N accepted is the one unforgivable failure of this pattern.
  • Strictly sequential: never dial two candidates concurrently.
  • At most one call per candidate per run. No retries within a run.
  • An ambiguous provider outcome must halt the live run for reconciliation; it must not automatically start another call or conflicting side effect. Only a clear yes in the structured result books the opening.
  • Do not expose credentials, and mask every phone number in output.
  • Treat medical, legal, financial, and emergency openings as logistics only: offer the time and the service name, give no advice on the call.

Output Format

After the run, report:

  • the opening, restated
  • per candidate attempted, in order: masked phone, terminal call status, and the structured accepted value (or the failure reason treated as a decline)
  • the outcome: filled by <name> or unfilled with why the run stopped (list exhausted, cap reached, or deadline passed)
  • candidates never called because the waterfall stopped early
  • how the user can re-run with the remaining candidates if the opening is still open

Never report the opening as filled unless exactly one candidate's structured result contains a clear acceptance.

Reference Implementation

A full runnable implementation of this pattern (with a waitlist data model, a dashboard, and tests that exercise the waterfall against a fake CALL-E server) lives in this repository at apps/typescript/ai-front-desk/ — see src/flows/backfill/backfillFlow.ts for the waterfall loop itself.

© 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 4 other files (scripts, references) in skills/priority-call-waterfall of CALLE-AI/awesome-phone-call-agents.

  • SKILL.md
  • references/examples.md
  • references/goal-and-result.md
  • references/safety.md
  • scripts/validate-waterfall-input.mjs

Open the folder on GitHubat commit 38d4118

Compare with similar skills

Priority Call Waterfall 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.

Priority Call Waterfall compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Priority Call Waterfall this skillCALLE-AI/awesome-phone-call-agents107—~1.5kAutomated safety check: PassMIT
Kubernetes Network Root Cause Analysiskubeshark/kubeshark12k—~5.3kAutomated safety check: PassApache-2.0
Nix Config Debugryan4yin/nix-config2.1k—~1.2kAutomated safety check: PassMIT
UModel Root Cause Analysisalibaba/UnifiedModel415—~1.9kAutomated safety check: PassCustom licence
Learningskortix-ai/suna20k—~1.1kAutomated safety check: PassCustom licence
Oncallpigweed-project/pigweed548—~963Automated safety check: PassApache-2.0

Similar skills

  • Kubernetes Network Root Cause Analysis

    kubeshark/kubeshark

    Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.

    12k GitHub stars~5.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Nix Config Debug

    ryan4yin/nix-config

    A skill your agent uses when something here is broken or stops working: an eval or build error, a failed activation, a dead or restarting unit, a mihomo or DNS outage, an unreachable host or MicroVM…

    2.1k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check passed

  • UModel Root Cause Analysis

    alibaba/UnifiedModel

    Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.

    415 GitHub stars~1.9k tokensUpdated 17 days ago
    DevOps & CloudAuto-check passed

  • Learnings

    kortix-ai/suna

    The project's episodic memory: a timestamped ledger of rules paid for with real outages and near-misses, one entry per incident.

    20k GitHub stars~1.1k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Oncall

    pigweed-project/pigweed

    Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).

    548 GitHub stars~963 tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Loop Triage Report

    cobusgreyling/loop-engineering

    Turns CI failures, open issues, recent commits and chat threads into a prioritized markdown report that an automation loop can act on without inventing architecture work.

    11k GitHub stars~500 tokensUpdated today
    DevOps & CloudAuto-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

Categories

Questions about Priority Call Waterfall

What does Priority Call Waterfall do?

Fill one open opportunity by calling a priority-ordered candidate list with CALL-E, one candidate at a time, until someone accepts — waitlist backfill, shift coverage, on-call escalation, and…. Priority Call Waterfall is an agent skill from CALLE-AI/awesome-phone-call-agents. Fill one open opportunity by calling a priority-ordered candidate list with CALL-E, one candidate at a time, until someone accepts — waitlist backfill, shift coverage, on-call escalation, and service dispatch workflows.

When should I use Priority Call Waterfall?

Priority Call Waterfall fits situations like: tasks that involve Incident response.

How do I install Priority Call Waterfall in Claude Code?

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

How do I install Priority Call Waterfall in Codex?

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

Can I use Priority Call Waterfall 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 priority-call-waterfall -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/priority-call-waterfall, .gemini/skills/priority-call-waterfall, .github/skills/priority-call-waterfall and .opencode/skills/priority-call-waterfall in your project.

What does Priority Call Waterfall need to run?

Going by SKILL.md and its folder, Priority Call Waterfall needs JavaScript for the scripts in its folder. Our summary lists: Node.js.

Does Priority Call Waterfall access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Priority Call Waterfall 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 Priority Call Waterfall use?

Priority Call Waterfall 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 Priority Call Waterfall use?

About 1.5k tokens (SKILL.md is roughly 6.2k 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 2k tokens, read only when the agent opens those files.

What are the alternatives to Priority Call Waterfall?

Skills that share tags, products or a category with Priority Call Waterfall: Kubernetes Network Root Cause Analysis (kubeshark/kubeshark, 12k stars), Nix Config Debug (ryan4yin/nix-config, 2.1k stars), UModel Root Cause Analysis (alibaba/UnifiedModel, 415 stars) and Learnings (kortix-ai/suna, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Priority Call Waterfall?

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.