Menu
Gets your commute time and route options, then texts you the details
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Ask a stronger Zo instance for planning, judgment, debugging guidance, or adjacent thinking through a minimal token-light oracle pattern using /zo/ask plus URL-based context drops.
Generate high-quality landing pages with anti-slop guardrails and multi-platform support. Creates modern, accessible designs for Zo.space, standalone HTML, and Next.js with professional aesthetics and clear typography hierarchy.
Maintain research repositories and a wiki-style compendium under Research/repos; scans existing knowledge folders before proposing repos, supports append-only intake, compaction, and repair sweeps for failed meeting-derived appends. Portable: owner/venture identity is externalized to a profile so the skill can ship publicly and be re-pointed on any Zo.
Portable Krisp transcript ingestion and meeting block pipeline for Zo Computer. Receives Krisp transcript webhooks or manual transcript files, normalizes meetings into repairable folders, optionally triangulates against calendar context, generates summary/metadata/decisions/action-item blocks, supports richer v3-style add-on blocks, archives monthly, and notifies the Zo owner when a meeting is partial or needs review.
Safe, archived Skill wrapper for the former standalone ZoATS applicant-tracking-system repo. Use when inspecting, packaging, validating, or exporting ZoATS as a reusable Zo skill scaffold; do not install live routes or run candidate/employer workflows on V's Zo without explicit approval.
Evaluate early-stage pitch decks across four investor credulity frames, stage-aware substantive rubric dimensions, optional named-POV reads, and markdown/JSON report rendering.
| name | text-commute-info |
| description | Gets your commute time and route options, then texts you the details |
| compatibility | Created for Zo Computer |
| metadata | {"author":"ian.zo.computer","category":"Community","display-name":"Text commute travel time and route","emoji":"🚏"} |
https://www.google.com/maps/dir/?api=1&origin=<ORIGIN>&destination=<DESTINATION>&travelmode=<TRAVELMODE> where <ORIGIN> is the user's provided origin, <DESTINATION> is the user's provided destination, and <TRAVELMODE> is the user's requested travel mode.tool open_webpage to navigate to the URL you constructed, then use tool view_webpage to inspect the route options.tool send_sms_to_user to relay the information from the page, giving them the top two travel options with their estimated travel time. If transit, explicitly list every train or bus line and transfer used in a route (e.g. Take the M, then G, then L). Also include the URL so the user can see the route on Google Maps. If they did not ask for a text, reply in the current chat instead.Rule or scheduled Agent. For example, a Rule could beWhen I text you asking for commute info, use `prompt Prompts/text-commute-info.prompt.md` but IGNORE step 4.
and a scheduled Agent could be set to run daily in the morning so that the user can be prepared for going to work or school. If the user explicitly wants this, use tool create_agent with SMS delivery and instruction:
Run `prompt Prompts/text-commute-info.prompt.md` with origin <ORIGIN>, destination <DESTINATION>, and travel mode <TRAVELMODE>, but IGNORE step 4