Agent skill

Verity Verification Core

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

Gate a CALL-E phone task's taskcompleted claim behind an independent transcript read-back before any real-world action.

MITAuto-check passed

Install Verity Verification Core

skills CLI
$ npx skills add CALLE-AI/awesome-phone-call-agents --skill verity-verification-core -a claude-code

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

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

At a glance

Gate a CALL-E phone task's taskcompleted claim behind an independent transcript read-back before any real-world action.

  • Works in 6 steps: Preview. Run scripts/preview_gate.py… → Get explicit user intent for that… → Place the call through your own CALL-E… → …
  • SKILL.md covers When to use, When not to use, Workflow and Quick start (no network, no…, plus 1 more section
  • Runs Python scripts from its folder; calls python and npm

What it does

Verity Verification Core is an agent skill from CALLE-AI/awesome-phone-call-agents. Gate a CALL-E phone task's taskcompleted claim behind an independent transcript read-back before any real-world action. Use after a confirm, reschedule, or book call to decide ALLOW or BLOCK, catch a mid-sentence self-correction, a voicemail, or a value the caller never actually confirmed, and get the exact value to re-confirm on a second channel. Deterministic, no network, fail-closed.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including scripts, reference files and assets (for example `assets/experience-a.call.json`, `assets/experience-a.input.json` and `assets/experience-b.call.json`).

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

  • “/verity-verification-core”

Requirements

  • Python 3
  • Node.js

Workflow steps

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

  1. Preview. Run scripts/preview_gate.py with your
  2. Get explicit user intent for that specific recipient and value before any call
  3. Place the call through your own CALL-E integration with the previewed plan.
  4. Re-fetch, don't trust the webhook. CALL-E does not sign webhooks; fetch
  5. Reconcile. Run scripts/reconcile_call.py with
  6. Act only on ALLOW. On BLOCK, open the second channel with repair_target,

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/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python
    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use npm, 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 no API keys, tokens, secrets or passwords.

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

Context cost

Verity Verification Core loads about 1.3k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 578 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
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
~4.6k

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). 578 words, ~1,251 tokens.

Download SKILL.mdSave it as .claude/skills/verity-verification-core/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.
name
verity-verification-core
description
Gate a CALL-E phone task's task_completed claim behind an independent transcript read-back before any real-world action. Use after a confirm, reschedule, or book call to decide ALLOW or BLOCK, catch a mid-sentence self-correction, a voicemail, or a value the caller never actually confirmed, and get the exact value to re-confirm on a second channel. Deterministic, no network, fail-closed.
license
MIT

Verity Verification Core

Use this skill in the gap between a CALL-E call finishing and your agent acting on it. CALL-E reports task_completed: true; this skill decides whether that is safe to act on. It re-reads transcript_turns with a deterministic grammar, checks the parsed value against what your action would actually write, requires a strict in-transcript confirmation, and folds in a fresh check of the resource you are about to change. Any missing field, any open ambiguity, any thrown error resolves to BLOCK, never ALLOW. task_completed == true is necessary, never sufficient.

It does not place calls, hold slots, or write calendars. It turns one call snapshot into ALLOW / BLOCK + a reason_code + a repair_target to confirm elsewhere.

When to use

  • After a CALL-E confirm, reschedule, or book call whose result will trigger a real-world write (a calendar entry, a CRM update, a fulfillment step).
  • When you need to tell "the caller agreed to 3:30" apart from "CALL-E's summary says 3:00", "the call reached voicemail", or "a time was mentioned but never confirmed".
  • When a caught failure should govern future calls: the skill can turn a blocked transcript into a PII-safe pattern for your own learned-pattern store.

When not to use

  • To place or schedule the call. That is your CALL-E integration's job — see references/calle-handoff.md.
  • As a source of the booking value. The value always comes from the deterministic grammar over the transcript, never from a model and never from CALL-E's summary.
  • For medical, legal, financial-advice, or emergency call content. See references/safety.md.

Workflow

  1. Preview. Run scripts/preview_gate.py with your intent + the value the task will write. It prints the call plan (task text, result_schema, a deterministic idempotency key, a masked recipient) and the exact E1–E7 checklist the gate will apply. No call is placed.
  2. Get explicit user intent for that specific recipient and value before any call is placed. Read references/safety.md.
  3. Place the call through your own CALL-E integration with the previewed plan.
  4. Re-fetch, don't trust the webhook. CALL-E does not sign webhooks; fetch GET /v1/calls/{id} server-side and reconcile that snapshot.
  5. Reconcile. Run scripts/reconcile_call.py with the call snapshot + the same intent/value. It prints ALLOW / BLOCK, the reason_code, and on BLOCK the repair_target to quote on a second channel (e.g. an SMS "reply YES to confirm 3:30"). Voicemail, self-correction, ambiguity, and an unconfirmed value are all reported as BLOCK, never as a verified result.
  6. Act only on ALLOW. On BLOCK, open the second channel with repair_target, or route to a human. Never let a BLOCK fall through to the write.
Show full SKILL.md (156 more words)Show less

Quick start (no network, no CALL-E account)

bash
cd skills/verity-verification-core

python scripts/preview_gate.py --input assets/experience-b.input.json
python scripts/reconcile_call.py --call assets/experience-b.call.json --input assets/experience-b.input.json
python scripts/self_test.py            # runs A / B / D, asserts each expected verdict

The bundled scripts use only the Python standard library and never open a socket. The reference implementation with full timezone handling is the TypeScript app at apps/typescript/verity-verification-core/ (npm install && npm run demo).

What the gate checks (E1–E7)

Requirement
E1task_completed == true and confidence is not low — necessary, never sufficient.
E2The transcript resolves to exactly one datetime after self-correction.
E3That parsed value exactly equals what the action would write (date + time + tz).
E4A bot turn restated the full value and the caller affirmed it (a bare "yes" after a partial restatement does not count).
E5No open ambiguity flag (self_correction_unresolved, multi_time_mention_unresolved, relative_date_ambiguity, no_explicit_confirmation, claim_parse_mismatch).
E6A fresh re-check shows the resource is still yours and not expired.
E7No learned failure pattern demands a second channel or a hard block.

All seven must hold together for ALLOW. Full walkthroughs of the three headline cases are in references/examples.md.

© 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 13 other files (scripts, references, assets) in skills/verity-verification-core of CALLE-AI/awesome-phone-call-agents.

  • SKILL.md
  • assets/experience-a.call.json
  • assets/experience-a.input.json
  • assets/experience-b.call.json
  • assets/experience-b.input.json
  • assets/experience-d.call.json
  • assets/experience-d.input.json
  • references/calle-handoff.md
  • references/examples.md
  • references/safety.md
  • scripts/preview_gate.py
  • scripts/reconcile_call.py
  • scripts/self_test.py
  • scripts/verity_gate.py

Open the folder on GitHubat commit 38d4118

Compare with similar skills

Verity Verification Core 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.

Verity Verification Core compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verity Verification Core this skillCALLE-AI/awesome-phone-call-agents107—~1.3kAutomated safety check: PassMIT
Claimsruvnet/ruflo74k1 repos~1.1kAutomated safety check: PassMIT
Gate Testsvercel/next.js143k—~2.8kAutomated safety check: PassMIT
Verification Before CompletionjnMetaCode/superpowers-zh8.3k—~443Automated safety check: PassMIT
PhoneBlockRunAI/ClawRouter6.6k—~2.4kAutomated safety check: PassMIT
Gateplugin87/ux-ui-agent-skills1.6k—~532Automated safety check: PassMIT

Similar skills

  • 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
  • Gate Tests

    vercel/next.js

    Official

    How to use the @gate / @force-gate test directives instead of it.skip or fake-green skip patterns.

    143k GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Verification Before Completion

    jnMetaCode/superpowers-zh

    Chinese-language rule that bars an agent from claiming work is done, fixed or passing until it has run a verification command and read the output.

    8.3k GitHub stars~443 tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed
  • Phone

    BlockRunAI/ClawRouter

    Verify phone numbers (carrier + SIM-swap fraud signals) and place AI-powered outbound voice calls via BlockRun's gateway (Twilio + Bland.ai).

    6.6k GitHub stars~2.4k tokensUpdated 5 days ago
    Auto-check passed
  • Gate

    plugin87/ux-ui-agent-skills

    Run the one-command quality gate and report the real N/N result.

    1.6k GitHub stars~532 tokensUpdated 3 days ago
    Frontend & DesignAuto-check passed
  • Verification Before Completion

    foryourhealth111-pixel/Vibe-Skills

    Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.

    3.6k GitHub stars~1.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-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 Verity Verification Core

What does Verity Verification Core do?

Gate a CALL-E phone task's taskcompleted claim behind an independent transcript read-back before any real-world action. Verity Verification Core is an agent skill from CALLE-AI/awesome-phone-call-agents. Gate a CALL-E phone task's taskcompleted claim behind an independent transcript read-back before any real-world action.

How do I install Verity Verification Core in Claude Code?

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

How do I install Verity Verification Core in Codex?

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

Can I use Verity Verification Core 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 verity-verification-core -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verity-verification-core, .gemini/skills/verity-verification-core, .github/skills/verity-verification-core and .opencode/skills/verity-verification-core in your project.

What does Verity Verification Core need to run?

Going by SKILL.md and its folder, Verity Verification Core needs Python for the scripts in its folder and the command-line tools its instructions call (python and npm). Our summary lists: Python 3; Node.js.

Does Verity Verification Core access the network?

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

Is Verity Verification Core 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 Verity Verification Core use?

Verity Verification Core 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 Verity Verification Core use?

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

What are the alternatives to Verity Verification Core?

Skills that share tags, products or a category with Verity Verification Core: Claims (ruvnet/ruflo, 74k stars), Gate Tests (vercel/next.js, 143k stars), Verification Before Completion (jnMetaCode/superpowers-zh, 8.3k stars) and Phone (BlockRunAI/ClawRouter, 6.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verity Verification Core?

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.