Agent skill

Accessible Outing Verifier

by CALLE-AI in 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.

MITAuto-check passedFrontend & Design

Install Accessible Outing Verifier

skills CLI

$ npx skills add CALLE-AI/awesome-phone-call-agents --skill accessible-outing-verifier -a claude-code

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

GitHub CLI

$ gh skill install CALLE-AI/awesome-phone-call-agents accessible-outing-verifier --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/accessible-outing-verifier .claude/skills/accessible-outing-verifier && 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/

Paste into Claude Code

Install the "accessible-outing-verifier" agent skill from https://github.com/CALLE-AI/awesome-phone-call-agents/tree/main/skills/accessible-outing-verifier into .claude/skills/accessible-outing-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessible-outing-verifier", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/CALLE-AI/awesome-phone-call-agents/tree/main/skills/accessible-outing-verifier

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add CALLE-AI/awesome-phone-call-agents --skill accessible-outing-verifier -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install CALLE-AI/awesome-phone-call-agents accessible-outing-verifier --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/accessible-outing-verifier .agents/skills/accessible-outing-verifier && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "accessible-outing-verifier" agent skill from https://github.com/CALLE-AI/awesome-phone-call-agents/tree/main/skills/accessible-outing-verifier into .agents/skills/accessible-outing-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessible-outing-verifier", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add CALLE-AI/awesome-phone-call-agents --skill accessible-outing-verifier -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install CALLE-AI/awesome-phone-call-agents accessible-outing-verifier --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/accessible-outing-verifier .cursor/skills/accessible-outing-verifier && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "accessible-outing-verifier" agent skill from https://github.com/CALLE-AI/awesome-phone-call-agents/tree/main/skills/accessible-outing-verifier into .cursor/skills/accessible-outing-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessible-outing-verifier", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/CALLE-AI/awesome-phone-call-agents.git --path skills/accessible-outing-verifier

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add CALLE-AI/awesome-phone-call-agents --skill accessible-outing-verifier -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install CALLE-AI/awesome-phone-call-agents accessible-outing-verifier --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/accessible-outing-verifier .gemini/skills/accessible-outing-verifier && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "accessible-outing-verifier" agent skill from https://github.com/CALLE-AI/awesome-phone-call-agents/tree/main/skills/accessible-outing-verifier into .gemini/skills/accessible-outing-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessible-outing-verifier", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install CALLE-AI/awesome-phone-call-agents accessible-outing-verifier

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add CALLE-AI/awesome-phone-call-agents --skill accessible-outing-verifier -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/accessible-outing-verifier .github/skills/accessible-outing-verifier && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "accessible-outing-verifier" agent skill from https://github.com/CALLE-AI/awesome-phone-call-agents/tree/main/skills/accessible-outing-verifier into .github/skills/accessible-outing-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessible-outing-verifier", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add CALLE-AI/awesome-phone-call-agents --skill accessible-outing-verifier -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install CALLE-AI/awesome-phone-call-agents accessible-outing-verifier --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/accessible-outing-verifier .opencode/skills/accessible-outing-verifier && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "accessible-outing-verifier" agent skill from https://github.com/CALLE-AI/awesome-phone-call-agents/tree/main/skills/accessible-outing-verifier into .opencode/skills/accessible-outing-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessible-outing-verifier", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: accessible-outing-verifier
GitHub stars: 107
Token cost: ~1.4k tokens
SKILL.md length: 650 words
Files: 7 (incl. scripts, references, assets)
Skills in repo: 101
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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.

Works in 3 steps: Establish Outing Profile & Digital Gap → Dry Run First — Always → Proposed Bounded CALL-E Verification…
Exploring unknown
SKILL.md covers When To Use, When Not To Use, Safety Boundaries and Workflow
Runs JavaScript scripts from its folder; calls node

What it does

Accessible Outing Verifier is an agent skill from 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts, reference files and assets (for example `assets/sample-outing-request.json`, `assets/sample-verdict-demoted.json` and `references/calle-task-schema.json`).

It sits in Frontend & Design, covering Accessibility. 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

Exploring unknown
Qualified venue claims without making calls

Example prompts

“Use the accessible-outing-verifier skill to demonstrate advisory accessibility-planning checks with offline fixtures and a proposed bounded CALL-E…”
“/accessible-outing-verifier”

Requirements

Node.js

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Establish Outing Profile & Digital Gap
Dry Run First — Always
Proposed Bounded CALL-E Verification Pattern

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.
Shell commands in SKILL.md call:
- node
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

Accessible Outing Verifier loads about 1.4k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 650 words of instructions outside code blocks.

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

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). 650 words, ~1,382 tokens.

Download SKILL.mdSave it as .claude/skills/accessible-outing-verifier/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.

name: accessible-outing-verifier
description: 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.
license: MIT

Accessible Outing Verifier

#accessible-outing-verifier

Use this skill when someone is planning an outing to a venue and has non-negotiable physical accessibility constraints (e.g. elevator working today, step-free path, accessible restroom width).

Planning an accessibility-sensitive outing (e.g., for a power wheelchair user, someone who is deaf, or a person with sensory sensitivities) currently relies on static online directory tags ("Wheelchair Accessible").

Where online data exists, it is often one flattened claim that hides daily operational reality:

The Elevator Paradox: A theater website lists an elevator, but is it operating today? Did maintenance sign off on it this morning?
The Qualified Guess: Venue staff may say "I think the ramp should be clear" or "The lift is usually fine". For a wheelchair user, a qualified guess can mean being stranded outside or facing physical danger.

The shipped helper reads supplied fixture labels and demonstrates how a qualified_confirmation can become UNKNOWN. It does not query a venue directory, interpret arbitrary speech, or place a call. The CALL-E schema and steps below are a proposed manual integration pattern, not an implemented live adapter. All findings are experimental and advisory; a person must verify critical conditions with the venue and plan a suitable backup before an outing.

Consult references/safety.md for explicit consent rules, phone number validation, and privacy boundaries before initiating any phone call.

When To Use

#when-to-use

Use this skill for:

someone planning an outing with non-negotiable physical accessibility requirements
published accessibility claims that require phone verification of current operational status
producing an auditable Feasibility Brief (FEASIBLE, NOT FULLY VERIFIED, or NOT FEASIBLE) with direct staff quotes and timestamps

When Not To Use

#when-not-to-use

Do not use this skill to:

conduct formal ADA or building code compliance audits; this verifies today's operational conditions, not legal certifications
make repeated nuisance calls to a business; strictly one call per venue per outing plan
call domestic or personal phone numbers; this is exclusively for public and commercial venues
place a phone call without the user's explicit consent to the specific question and target phone number

Show full SKILL.md (312 more words)Show less

Safety Boundaries

#safety-boundaries

Read references/safety.md for full requirements. Core rules:

Offline Only: Every supported execution evaluates local fixtures. --real is unsupported and refused; no socket is opened, no credits are spent, and no phone is dialed.
Demonstrated Demotion Rule: The fixed example maps qualified_confirmation to UNKNOWN. It does not detect every hedge, validate an extraction, or establish physical safety.
Proposed Consent Gate: Any future live integration must request explicit authorization for the exact venue and question before dialing. Printed fixture authorization is not consent.
Data Privacy & Masking: Use synthetic profiles only. The helper masks the phone field; venue names, persona text and other free text are not a general-purpose privacy filter. A future call must disclose no personal patron or medical details.
Fail-Closed Principle: If a call fails, times out, or encounters a busy line, the verdict is NEEDS_HUMAN_REVIEW or NOT FULLY VERIFIED—never an assumed pass.

Workflow

1. Establish Outing Profile & Digital Gap

Define the venue and constraints in a profile JSON:

json

{
  "venue_name": "The Grand Theater",
  "phone": "+15555550199",
  "persona": "Power Wheelchair User",
  "constraints": [
    { "id": "c1", "category": "daily_operational", "label": "Main Elevator Operating Today", "critical": true },
    { "id": "c2", "category": "static_facility", "label": "Step-Free Main Entrance", "critical": true }
  ]
}

2. Dry Run First — Always

Run the standalone helper script scripts/verify-outing.mjs against offline test fixtures:

bash

node scripts/verify-outing.mjs --profile assets/sample-outing-request.json

See references/examples.md for sample command output and scenario verdicts.

3. Proposed Bounded CALL-E Verification Pattern

No live runner is included. A future operator-controlled integration can use the schema in references/calle-task-schema.json, after confirming an authorized E.164 venue destination and reviewing the exact question. Stop on an unknown submission or result; do not automatically redial. Explain that a submitted call may continue after closing the host. This is information gathering, not emergency assistance, medical advice, or authorization to dispatch a person.

The proposed normalizer would evaluate extracted labels, subject to human verification; the shipped helper demonstrates only the qualified-confirmation fixture:

confirmed -> Constraint marked PASSED.
qualified_confirmation ("I think it should be working...") -> Demoted to UNKNOWN. Outing verdict: NOT FULLY VERIFIED.
refuted ("Elevator is undergoing repairs today") -> Constraint marked FAILED. Outing verdict: NOT FEASIBLE.

Files

SKILL.md and 6 other files (scripts, references, assets) in skills/accessible-outing-verifier of CALLE-AI/awesome-phone-call-agents.

SKILL.md
assets/sample-outing-request.json
assets/sample-verdict-demoted.json
references/calle-task-schema.json
references/examples.md
references/safety.md
scripts/verify-outing.mjs

Open the folder on GitHubat commit 38d4118

Compare with similar skills

Accessible Outing Verifier 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.

Accessible Outing Verifier compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Accessible Outing Verifier this skillCALLE-AI/awesome-phone-call-agents	107	—	~1.4k	Automated safety check: Pass	MIT	today
Web Interface Guidelines Reviewervercel-labs/openreview	1.7k	97 repos	~308	Automated safety check: Pass	None	7 mo ago
Accessibility Reviewmarkmead/hyperui	12k	1 repos	~1.1k	Automated safety check: Pass	MIT	14 days ago
Web Animation DesignbaptisteArno/typebot.io	11k	2 repos	~2.7k	Automated safety check: Pass	Custom licence	3 days ago
Accessibility Fixeribelick/ui-skills	9.6k	4 repos	~1.2k	Automated safety check: Pass	MIT	yesterday
Wcag Audit PatternsvmDeshpande/ai-agent-automation	178	11 repos	~610	Automated safety check: Pass	Apache-2.0	28 days ago

Similar skills

Web Interface Guidelines Reviewer
vercel-labs/openreview
Official
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
1.7k GitHub starsUsed in 97 repos~308 tokens
Frontend & DesignAuto-check passed
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
12k GitHub starsUsed in 1 repo~1.1k tokens
Frontend & DesignAuto-check passed
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
11k GitHub starsUsed in 2 repos~2.7k tokens
Frontend & DesignAuto-check passed
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
9.6k GitHub starsUsed in 4 repos~1.2k tokens
Frontend & DesignAuto-check passed
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
178 GitHub starsUsed in 11 repos~610 tokens
Frontend & DesignAuto-check passed
Baseline UI
ibelick/ui-skills
Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.
9.6k GitHub starsUsed in 8 repos~855 tokens
Frontend & DesignAuto-check passed

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

All 101 skills in this repo

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 today
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 today
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 today
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 today
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 today
Auto-check passed
Znak Callops
CALLE-AI/awesome-phone-call-agents
Ask a service provider about availability and price in one authorized phone call, then return full transcript quotations and explicit unknowns without booking anything.
107 GitHub stars~1.1k tokensUpdated today
Auto-check passed

Questions about Accessible Outing Verifier

What does Accessible Outing Verifier do?

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. Accessible Outing Verifier is an agent skill from 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.

When should I use Accessible Outing Verifier?

Accessible Outing Verifier fits situations like: exploring unknown; qualified venue claims without making calls.

How do I install Accessible Outing Verifier in Claude Code?

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

How do I install Accessible Outing Verifier in Codex?

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

Can I use Accessible Outing Verifier 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 accessible-outing-verifier -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/accessible-outing-verifier, .gemini/skills/accessible-outing-verifier, .github/skills/accessible-outing-verifier and .opencode/skills/accessible-outing-verifier in your project.

What does Accessible Outing Verifier need to run?

Going by SKILL.md and its folder, Accessible Outing Verifier needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.

Does Accessible Outing Verifier 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 Accessible Outing Verifier 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 Accessible Outing Verifier use?

Accessible Outing Verifier 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 Accessible Outing Verifier use?

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

What are the alternatives to Accessible Outing Verifier?

Skills that share tags, products or a category with Accessible Outing Verifier: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Accessible Outing Verifier?

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.

Install Accessible Outing Verifier

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Accessible Outing Verifier

When To Use

When Not To Use

Safety Boundaries

Workflow

1. Establish Outing Profile & Digital Gap

2. Dry Run First — Always

3. Proposed Bounded CALL-E Verification Pattern

Files

Compare with similar skills

Similar skills

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

Related

Questions about Accessible Outing Verifier