agentleFS
FoneClaw-AIFoneClaw-AI/foneclaw-android/skills/navigation/SKILL.md

RoutePlanningNavigationSkill

Skill21 starsChanged 4 months agoMITView on GitHub

This skill is used by an Android Agent to plan a route and open a navigation session in a map application.

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. About 0 are common, 17 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈17

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start route navigation for the user using an appropriate map application and travel mode.

    line 20
  2. Distinctive:

    If no map application is installed, notify the user:

    line 35
  3. Distinctive:

    If a selected application is not installed or its package name cannot be resolved, skip it and continue to the next priority.

    line 44
  4. Distinctive:

    If randomly selecting a map application, choose only from installed map applications with a known package name.

    line 45
  5. Distinctive:

    Use the phone’s current location to get the latitude and longitude.

    line 52
  6. Distinctive:

    If location retrieval fails, notify the user:

    line 53
  7. Distinctive:

    Check whether the user has previously navigated to the target destination.

    line 59
  8. Distinctive:

    If the destination exists in navigation history, directly complete the full destination information.

    line 60
  9. Distinctive:

    If no matching destination exists, determine whether the user’s input contains enough information to identify the destination.

    line 61
  10. Distinctive:

    If the destination cannot be determined with enough confidence, ask the user to provide more information.

    line 62
  11. Distinctive:

    If the user has not specified a travel mode, check whether a user travel mode preference exists.

    line 66
  12. Distinctive:

    If no user travel mode preference exists, get the phone’s current location.

    line 67
  13. Distinctive:

    If location retrieval succeeds, determine the best travel mode based on the relationship between the current location and the destination.

    line 72
  14. Very specific:

    After determining the map application name, map application package name, destination, and travel mode, call map_navigate once.

    line 84
  15. Distinctive:

    No map application is installed.

    line 96
  16. Distinctive:

    Do not ask the user for missing information unless the destination cannot be determined.

    line 104
  17. Very specific:

    Always resolve and pass the selected map application package name to map_navigate.

    line 106
  18. Very specific:

    Never call retired route-specific tools such as map_drive or map_walk.

    line 107
  19. Distinctive:

    Prefer navigation history when it can complete the destination.

    line 108
  20. Distinctive:

    Use current phone location as the starting point.

    line 109

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Route Navigation Planning Agent Skill

Skill Name

Route Navigation Planning

Description

This skill is used by an Android agent to plan and start route navigation based on the user’s destination, preferred map application, current phone location, installed map applications, last used map application, and travel mode.

The agent should determine the map application name and package name, starting point, destination, and travel mode, then invoke the corresponding map navigation tool and monitor the screen until the target map application enters navigation mode.

Goal

Start route navigation for the user using an appropriate map application and travel mode.

Required Tools

  • get_installed_map_apps
  • get_location
  • map_navigate

Workflow

1. Determine the Map Application

The selected map application must include both the application display name and the package name. The package name is required when invoking the map navigation tool because deep links may fail or open the wrong target without it.

  1. Get the list of currently installed map applications on the phone, including each application’s display name and package name.
  2. If no map application is installed, notify the user:

    No map application is currently available. Task terminated.

  3. Select the map application using the following priority order:
    • The map application explicitly specified in the user’s current input.
    • The map application extracted from user preferences.
    • The last used map application.
    • A randomly selected installed map application.
  4. If a selected application is not installed or its package name cannot be resolved, skip it and continue to the next priority.
  5. If randomly selecting a map application, choose only from installed map applications with a known package name.
  6. The final selected map application must be represented as:
    • map_app_name
    • map_app_package_name

2. Determine the Starting Point

  1. Use the phone’s current location to get the latitude and longitude.
  2. If location retrieval fails, notify the user:

    Failed to get location.

3. Determine the Destination

  1. Check whether the user has previously navigated to the target destination.
  2. If the destination exists in navigation history, directly complete the full destination information.
  3. If no matching destination exists, determine whether the user’s input contains enough information to identify the destination.
  4. If the destination cannot be determined with enough confidence, ask the user to provide more information.

4. Determine the Travel Mode

  1. If the user has not specified a travel mode, check whether a user travel mode preference exists.
  2. If no user travel mode preference exists, get the phone’s current location.
  3. If location retrieval fails, notify the user:

    Failed to get location.

  4. If location retrieval succeeds, determine the best travel mode based on the relationship between the current location and the destination.

Map the selected travel mode to exactly one supported travelMode value:

  • Driving: driving
  • Walking: walking
  • Cycling: bicycling
  • Electric bicycle: electric_bicycling
  • Public transportation: public_transport

5. Start Map Navigation

  1. After determining the map application name, map application package name, destination, and travel mode, call map_navigate once.
  2. Pass the resolved destination as destination and the exact value from the travel mode mapping as travelMode.
  3. Pass packageName=map_app_package_name. Do not pass the application display name as packageName.

Completion Criteria

The task is complete when the selected map application successfully enters the corresponding navigation mode.

Failure Conditions

The skill should terminate and notify the user when any of the following occurs:

  1. No map application is installed.
  2. The phone location cannot be retrieved.
  3. The destination cannot be determined and the user does not provide enough additional information.
  4. The selected map application package name cannot be resolved.
  5. The map navigation tool fails to open navigation.

Agent Behavior Requirements

  • Do not ask the user for missing information unless the destination cannot be determined.
  • Select the map application in this order: user’s current input, extracted user preference, last used map application, random installed map application.
  • Always resolve and pass the selected map application package name to map_navigate.
  • Never call retired route-specific tools such as map_drive or map_walk.
  • Prefer navigation history when it can complete the destination.
  • Use current phone location as the starting point.
  • Select the map application automatically when the user does not specify one.
  • Select the travel mode automatically when the user does not specify one.
  • Automatically handle location permission dialogs and common blocking pop-ups.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.