Agent skill

Landmark Navigation Assist

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

MITAuto-check passed

Install Landmark Navigation Assist

skills CLI
$ npx skills add CALLE-AI/awesome-phone-call-agents --skill landmark-navigation-assist -a claude-code

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

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

At a glance

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…

  • Works in 4 steps: Author a location config matching… → Validate it —… → Call buildCallTask(config, { appName })… → …
  • A driver requests navigation help for an address that already has known landmark/approach notes
  • SKILL.md covers Key Features, When to Use, When Not to Use and How It Works, plus 5 more sections
  • Runs JavaScript scripts from its folder

What it does

Landmark Navigation Assist is an agent skill from 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 instead of GPS or postal text. Use when a driver requests navigation help for an address that already has known landmark/approach notes; not for addresses with no config, and not as a replacement for turn-by-turn GPS on the earlier, unambiguous part of a route.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/sample-location-config.json`, `package.json` and `references/examples.md`).

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

  • A driver requests navigation help for an address that already has known landmark/approach notes
  • Not for addresses with no config
  • Not as a replacement for turn-by-turn GPS on the earlier
  • Unambiguous part of a route

Example prompts

  • “Use the landmark-navigation-assist skill to turn a pre-written, building-level location config into a CALL-E outbound phone-call task that guides a…”
  • “/landmark-navigation-assist”

Requirements

  • Node.js

Workflow steps

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

  1. Author a location config matching references/location-config.schema.json (see assets/sample-location-config.json for a filled-in example)…
  2. Validate it — scripts/locationConfigSchema.js is a Zod schema mirroring the JSON Schema, useful if you're loading configs at runtime in a…
  3. Call buildCallTask(config, { appName }) from scripts/buildCallTask.js to get the task string and matching resultSchema.
  4. Fire the call with the CALL-E SDK

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

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

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    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

Landmark Navigation Assist loads about 1.6k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 121 tokens; SKILL.md has 725 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~121
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.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). 725 words, ~1,603 tokens.

Download SKILL.mdSave it as .claude/skills/landmark-navigation-assist/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
landmark-navigation-assist
description
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 instead of GPS or postal text. Use when a driver requests navigation help for an address that already has known landmark/approach notes; not for addresses with no config, and not as a replacement for turn-by-turn GPS on the earlier, unambiguous part of a route.
license
MIT

Landmark Navigation Assist

Purpose: Turns a pre-written, building-level location config into a CALL-E task instruction that guides a delivery driver (or repeat ride-hailing pickup) through the last few hundred meters to a specific building, using landmarks instead of GPS/text directions. Built for addresses where map pins and postal text routinely fail — landmark-based, informally-numbered, or newly-built areas — and the driver's own support call would otherwise be the fallback.

Not an address-reader. It's a guided conversation: the agent asks which direction the driver is approaching from, gives turn-by-turn landmark instructions for that direction, confirms the building by its distinguishing features, and only offers a human escalation contact if the driver is still stuck after being guided.

Key Features

  • Config-driven, not hardcoded. One JSON config per physical building (see references/location-config.schema.json), authored once and reused for every delivery to that address — this is what makes the skill reusable across locations rather than a one-off script for a single address.
  • Direction-aware disambiguation. The config supports multiple approach_from entries; the agent asks the driver which landmark they recognize and picks the matching guidance, rather than reading one fixed set of directions regardless of where the driver actually is.
  • In-call escalation only, driver-confirmed. If the driver is still stuck after being guided, the agent offers a human contact number — it never escalates automatically, and escalation resolves entirely within the same call (the agent reads the number aloud, the driver dials it themselves after hanging up). No webhook, no second outbound call, no SMS.
  • Structured result, not free-text parsing. Pairs with CALL-E's resultSchema to return escalation_offered, escalation_number_revealed, and resolution_summary as typed fields instead of requiring you to parse a transcript.

When to Use

  • Recurring deliveries/pickups to the same physical address, where investing in a one-time config pays off over repeat visits.
  • Addresses where the failure mode is specifically "driver is nearby but can't identify the exact building" — not a wrong address, not a closed business, not a road closure.
  • Opt-in, driver-initiated help (e.g. a "request navigation help" button in a delivery app) — this skill assumes the call is triggered by an explicit driver action, not a proactive push CALL-E makes to every delivery.

When Not to Use

  • One-off deliveries to addresses with no config authored yet — there's no fallback to generic map directions built in; if there's no config for the address, this skill has nothing to say.
  • As a replacement for real-time GPS navigation for the earlier, non-ambiguous part of a route — this is specifically for the "last few hundred meters" failure mode, not full trip navigation.
  • Anywhere a live human handoff (warm transfer) is required — this skill only reveals a callback number for the driver to dial themselves; it does not transfer the call.
Show full SKILL.md (302 more words)Show less

How It Works

  1. Author a location config matching references/location-config.schema.json (see assets/sample-location-config.json for a filled-in example). One config per building, not per delivery or per resident — unit-specific details live in the config's optional units[] array and are looked up at call time.

  2. Validate it — scripts/locationConfigSchema.js is a Zod schema mirroring the JSON Schema, useful if you're loading configs at runtime in a Node.js project and want a readable validation error instead of a malformed call task.

  3. Call buildCallTask(config, { appName }) from scripts/buildCallTask.js to get the task string and matching resultSchema.

  4. Fire the call with the CALL-E SDK:

    js
    import { buildCallTask, resultSchema } from "./scripts/buildCallTask.js";
    
    const { task } = { task: buildCallTask(config, { appName: "YourApp" }) };
    
    const call = await client.calls.createAndWait({
      task,
      recipient: {
        phone: driverPhone,
        region: config.address.region_code,
        locale: config.language.locale,
      },
      resultSchema,
    });

Output Structure

structuredResult on the completed call:

json
{
  "escalation_offered": false,
  "escalation_number_revealed": false,
  "resolution_summary": "The driver was guided to the building and confirmed finding it before the call ended."
}

Safety and Side Effects

This skill places a real outbound phone call. See references/safety.md for the full safety contract (explicit user intent, phone number handling, escalation boundaries, cancellation behavior). Summary: outbound-only, driver-initiated, no automated escalation action, no webhook/second call/SMS, no recurring schedule to cancel.

Compatibility Notes

  • Plain Node.js (ESM), no build step, no framework dependency for scripts/. Requires zod if you use locationConfigSchema.js.
  • Requires a CALL-E API key and the @call-e/calle SDK (or equivalent HTTP calls to POST /v1/calls).
  • Check docs.heycall-e.com/regions before deploying to a new country — CALL-E currently classifies destination countries as "Local line" (reliable, production-ready) or "International line" (testing-only, lower reliability). Build and demo this skill with that in mind; don't assume every region behaves identically.

Requirements

  • Node.js 18+ (uses node:fs, ESM, top-level await in examples).
  • @call-e/calle SDK and a CALL-E API key.
  • zod (only if using the provided schema validator).

Full Demo Application

A complete reference implementation — including a second real-world config, a "request help" trigger page with masked-number escalation reveal, and real-call test tooling — lives at github.com/sadiq1745/call-E.

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

  • SKILL.md
  • assets/sample-location-config.json
  • package.json
  • references/examples.md
  • references/location-config.schema.json
  • references/safety.md
  • scripts/buildCallTask.js
  • scripts/locationConfigSchema.js

Open the folder on GitHubat commit 38d4118

Compare with similar skills

Landmark Navigation Assist 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.

Landmark Navigation Assist compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Landmark Navigation Assist this skillCALLE-AI/awesome-phone-call-agents107—~1.6kAutomated safety check: PassMIT
Navigation Landmarkthedaviddias/Front-End-Checklist74k—~417Automated safety check: PassMIT
Alfworld Location Navigatorzjunlp/SkillNet1.4k—~320Automated safety check: PassMIT
Breadcrumb Navigationthedaviddias/Front-End-Checklist74k—~418Automated safety check: PassMIT
Keyboard Navigationthedaviddias/Front-End-Checklist74k—~567Automated safety check: PassMIT
Landmark Regionsthedaviddias/Front-End-Checklist74k—~449Automated safety check: PassMIT

Similar skills

  • Navigation Landmark

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Use navigation landmark regions.

    74k GitHub stars~417 tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed
  • Moves the agent to a specified receptacle or object location within the Alfworld environment.

    1.4k GitHub stars~320 tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Breadcrumb Navigation

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Implement accessible breadcrumb navigation.

    74k GitHub stars~418 tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed
  • Keyboard Navigation

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Enable keyboard navigation for all elements.

    74k GitHub stars~567 tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed
  • Landmark Regions

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Use landmark regions correctly.

    74k GitHub stars~449 tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed
  • Skip Navigation

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Include a skip navigation link.

    74k GitHub stars~443 tokensUpdated 5 days ago
    Frontend & DesignAuto-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
  • 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
  • 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 yesterday
    Auto-check passed

Questions about Landmark Navigation Assist

What does Landmark Navigation Assist do?

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…. Landmark Navigation Assist is an agent skill from 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 instead of GPS or postal text.

When should I use Landmark Navigation Assist?

Landmark Navigation Assist fits situations like: A driver requests navigation help for an address that already has known landmark/approach notes; not for addresses with no config; not as a replacement for turn-by-turn GPS on the earlier; unambiguous part of a route.

How do I install Landmark Navigation Assist in Claude Code?

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

How do I install Landmark Navigation Assist in Codex?

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

Can I use Landmark Navigation Assist 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 landmark-navigation-assist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/landmark-navigation-assist, .gemini/skills/landmark-navigation-assist, .github/skills/landmark-navigation-assist and .opencode/skills/landmark-navigation-assist in your project.

What does Landmark Navigation Assist need to run?

Going by SKILL.md and its folder, Landmark Navigation Assist needs JavaScript for the scripts in its folder. Our summary lists: Node.js.

Does Landmark Navigation Assist access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Landmark Navigation Assist 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 Landmark Navigation Assist use?

Landmark Navigation Assist 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 Landmark Navigation Assist use?

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

What are the alternatives to Landmark Navigation Assist?

Skills that share tags, products or a category with Landmark Navigation Assist: Navigation Landmark (thedaviddias/Front-End-Checklist, 74k stars), Alfworld Location Navigator (zjunlp/SkillNet, 1.4k stars), Breadcrumb Navigation (thedaviddias/Front-End-Checklist, 74k stars) and Keyboard Navigation (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Landmark Navigation Assist?

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.