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

Bounty Screening Call

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

Verify public bounty facts by one explicitly authorized CALL-E phone call before an agent claims or submits work, returning evidence-backed reward, AI-use, eligibility, deadline, payout, and…

MITAuto-check passed

Install Bounty Screening Call

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

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

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

At a glance

Verify public bounty facts by one explicitly authorized CALL-E phone call before an agent claims or submits work, returning evidence-backed reward, AI-use, eligibility, deadline, payout, and…

  • Works in 5 steps: Confirm that the listing URL is HTTPS… → Validate organizer_phone_e164 with… → Confirm the current operator intent and… → …
  • SKILL.md covers When To Use, When Not To Use, Required Inputs and Preflight And Preview, plus 4 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Bounty Screening Call is an agent skill from CALLE-AI/awesome-phone-call-agents. Verify public bounty facts by one explicitly authorized CALL-E phone call before an agent claims or submits work, returning evidence-backed reward, AI-use, eligibility, deadline, payout, and submission details while keeping every external commitment under human review.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/example-input.json`, `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

  • “/bounty-screening-call”

Requirements

  • Python 3

Workflow steps

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

  1. Confirm that the listing URL is HTTPS and that the organizer and facts are
  2. Validate organizer_phone_e164 with ^\+[1-9]\d{6,14}$. Reject local,
  3. Confirm the current operator intent and the contact basis. Do not infer
  4. Compile a preview containing the masked destination, exact task text,
  5. Freeze the preview. Any change to recipient, task, schema, listing, or

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

    Shell commands in SKILL.md call:

    • python3

    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

Bounty Screening Call loads about 1.9k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 798 words of instructions outside code blocks.

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

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). 798 words, ~1,886 tokens.

Download SKILL.mdSave it as .claude/skills/bounty-screening-call/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
bounty-screening-call
description
Verify public bounty facts by one explicitly authorized CALL-E phone call before an agent claims or submits work, returning evidence-backed reward, AI-use, eligibility, deadline, payout, and submission details while keeping every external commitment under human review.
license
MIT

Bounty Screening Call

Use this skill when an agent has found a potentially legitimate technical bounty or contest and needs to verify unresolved public facts with the official organizer before doing claim or submission work. The skill is a fact-gathering step, not an application, claim, negotiation, payment, or payout-collection workflow.

The default path is a local preview. A compatible host may hand the frozen call task to CALL-E only after the operator has explicitly authorized that one call, confirmed the destination, and reviewed the preview. Read references/safety.md before any live handoff and use references/examples.md for the offline fixtures.

When To Use

  • A public bounty listing has an official organizer contact but one or more of reward, AI-use, eligibility, deadline, payout, or submission facts are not independently confirmed.
  • The operator wants a transcript-backed verification brief before deciding whether to invest engineering time or submit a claim.
  • A host can preserve one stable request identifier and reconcile the terminal CALL-E result before any downstream action.

When Not To Use

  • To call a guessed, scraped, private, or unrelated number.
  • To ask for passwords, one-time codes, identity documents, bank/card details, payment credentials, PayPal links, or account access.
  • To negotiate a reward, reserve a slot, submit a solution, accept legal terms, create an account, or promise delivery.
  • To decide automatically that a bounty is safe, accepted, payable, or worth claiming. The result is advisory evidence for a human or a separate deterministic policy gate.
  • For legal, tax, banking, or financial-advice questions. Ask only about the public payout route and record uncertainty.

Required Inputs

  • request_id: stable identifier for this one verification request.
  • opportunity_id: stable listing or issue identifier.
  • title: public bounty title.
  • listing_url: HTTPS URL of the official listing or issue.
  • organizer_name: public organizer or project name.
  • organizer_phone_e164: one destination explicitly supplied or authorized by the operator; E.164 only.
  • contact_basis: why the operator may contact this number (for example, an organizer-published support line plus the operator's current intent to call).
  • reported_reward: amount and currency currently shown in public evidence.
  • reported_ai_policy: allowed, limited, forbidden, or unknown.
  • reported_eligibility: eligible, ineligible, or unknown for the operator's jurisdiction.
  • reported_deadline: ISO date/time or unknown.
  • reported_payout_method: fiat, crypto, other, or unknown.
  • public_evidence: short citations or quotes from the listing. Do not put secrets or private contact data here.
  • operator_intent: an explicit statement that this single verification call is authorized now.

Preflight And Preview

  1. Confirm that the listing URL is HTTPS and that the organizer and facts are public. A public number alone is not permission to call it.
  2. Validate organizer_phone_e164 with ^\\+[1-9]\\d{6,14}$. Reject local, guessed, extension-only, or malformed numbers.
  3. Confirm the current operator intent and the contact basis. Do not infer permission from a search result, an issue comment, or silence.
  4. Compile a preview containing the masked destination, exact task text, result schema, and stable idempotency key. The preview must state call_placed: false.
  5. Freeze the preview. Any change to recipient, task, schema, listing, or request identifier requires a new preview and new approval.

The bundled preview fixture is dependency-free and never contacts CALL-E:

bash
python3 scripts/preview_bounty_screen.py assets/example-input.json
Show full SKILL.md (292 more words)Show less

CALL-E Task Contract

After the preview has been reviewed, a host may use CALL-E's plan/run/status flow or an SDK equivalent. Planning is not dialing. Preserve the returned call/run identifier and stable idempotency key; do not repeat a run after an ambiguous timeout.

Use a goal equivalent to:

text
You are a verification-only automated assistant calling on behalf of the
operator. Disclose that immediately and speak only with the official organizer
or an authorized representative.

Verify public facts about one technical bounty: the reward amount and currency,
whether AI assistance is allowed, jurisdiction eligibility, deadline, payout
method, and official submission URL. Do not claim the bounty, negotiate, submit
anything, create an account, or request passwords, codes, identity documents,
bank/card details, payment credentials, PayPal links, or private data.

If the wrong person, voicemail, refusal, or uncertainty is encountered, record
unknown and end politely. Return only the exact structured result fields and
short public-fact notes. Do not infer a confirmation from silence.

The host must pass the frozen organizer_phone_e164, without printing it in human-facing output, and must use one call at most for this request.

Structured Result

The provider result must be reconciled against evidence, not trusted merely because a model populated a field:

json
{
  "reward_status": "confirmed | unconfirmed | contradicted",
  "reward_amount": "number or null",
  "reward_currency": "string or null",
  "ai_use": "allowed | limited | forbidden | unknown",
  "eligibility": "eligible | ineligible | unknown",
  "deadline": "ISO string or null",
  "payout_method": "fiat | crypto | other | unknown",
  "submission_url": "HTTPS string or null",
  "confidence": "high | medium | low",
  "notes": "public facts only",
  "evidence": [
    {"claim": "reward", "transcript_span": "short supporting span"}
  ]
}

Use unknown or unconfirmed when the organizer did not clearly establish a fact. A completed call does not mean the bounty was accepted or awarded.

Downstream Decision Boundary

Pass the reconciled public facts to a separate deterministic task policy. A verification result may support a human decision, but it must never by itself:

  • claim an issue or accept contest terms;
  • submit code, a form, a PR, or an account registration;
  • send a message asserting acceptance;
  • request, store, or validate payout credentials; or
  • trigger payment, recurring calls, or another external mutation.

If the bounty is accepted later, monitor the platform or approved mailbox separately for a written payout request. Never place payout credentials in a public issue, PR, transcript, fixture, or log.

Cancellation And Ambiguity

Withhold the provider run approval to cancel before dialing. After a call is accepted by CALL-E, closing the host does not necessarily cancel it; report that limitation honestly. If the call id is missing, status polling times out, or the provider response is otherwise ambiguous, stop and route to human review. Do not redial automatically or start another bounty workflow for the same request.

See references/safety.md for the complete live-call boundary and references/examples.md for safe, ambiguous, and prohibited cases.

© 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, assets) in skills/bounty-screening-call of CALLE-AI/awesome-phone-call-agents.

  • SKILL.md
  • assets/example-input.json
  • references/examples.md
  • references/safety.md
  • scripts/preview_bounty_screen.py

Open the folder on GitHubat commit 38d4118

Compare with similar skills

Bounty Screening Call 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.

Bounty Screening Call compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bounty Screening Call this skillCALLE-AI/awesome-phone-call-agents107—~1.9kAutomated safety check: PassMIT
Hermes Agent Skill AuthoringNousResearch/hermes-agent252k—~3.6kAutomated safety check: PassMIT
No Explicit Anythedaviddias/Front-End-Checklist74k—~565Automated safety check: PassMIT
Configuring Oauth2 Authorization Flowmukul975/Anthropic-Cybersecurity-Skills34k—~1.7kAutomated safety check: PassApache-2.0
Authoring Skillsvercel/next.js143k—~1kAutomated safety check: PassMIT
Abp Authorizationabpframework/abp14k—~1.3kAutomated safety check: PassLGPL-3.0

Similar skills

  • Hermes Agent Skill Authoring

    NousResearch/hermes-agent

    Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.

    252k GitHub stars~3.6k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • No Explicit Any

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing TypeScript files for type safety regressions, during code review of functions that handle external data, or when the codebase has ESLint warnings for…

    74k GitHub stars~565 tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Configuring Oauth2 Authorization Flow

    mukul975/Anthropic-Cybersecurity-Skills

    Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token…

    34k GitHub stars~1.7k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • Authoring Skills

    vercel/next.js

    Official

    How to create and maintain agent skills in .agents/skills/. An agent skill from vercel/next.js.

    143k GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Abp Authorization

    abpframework/abp

    ABP permission system - PermissionDefinitionProvider, [Authorize] attribute, CheckPolicyAsync, IsGrantedAsync, ICurrentUser, IPermissionManager, multi-tenancy side.

    14k GitHub stars~1.3k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Implementing GCP Binary Authorization

    mukul975/Anthropic-Cybersecurity-Skills

    Implements GCP Binary Authorization end to end, including creating KMS-backed attestors, Container Analysis notes, deploy-time policies, and signing image attestations, so that only trusted…

    34k GitHub stars~2k tokensUpdated 1 mo ago
    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

Questions about Bounty Screening Call

What does Bounty Screening Call do?

Verify public bounty facts by one explicitly authorized CALL-E phone call before an agent claims or submits work, returning evidence-backed reward, AI-use, eligibility, deadline, payout, and…. Bounty Screening Call is an agent skill from CALLE-AI/awesome-phone-call-agents. Verify public bounty facts by one explicitly authorized CALL-E phone call before an agent claims or submits work, returning evidence-backed reward, AI-use, eligibility, deadline, payout, and submission details while keeping every external commitment under human review.

How do I install Bounty Screening Call in Claude Code?

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

How do I install Bounty Screening Call in Codex?

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

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

What does Bounty Screening Call need to run?

Going by SKILL.md and its folder, Bounty Screening Call needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Bounty Screening Call 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 Bounty Screening Call 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 Bounty Screening Call use?

Bounty Screening Call 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 Bounty Screening Call use?

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

What are the alternatives to Bounty Screening Call?

Skills that share tags, products or a category with Bounty Screening Call: Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars), No Explicit Any (thedaviddias/Front-End-Checklist, 74k stars), Configuring Oauth2 Authorization Flow (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Authoring Skills (vercel/next.js, 143k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bounty Screening Call?

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.