Goplaces
Purpose
Query Google Places API (New) via the goplaces CLI for text search, place details, resolve, and reviews. Use for human-friendly place lookup or JSON output for scripts.
Routing
- Use when: Use when the user asks to query Google Places API New via the goplaces CLI for text search, place details, resolve, and reviews. Use for human-friendly place lookup or JSON output for scripts.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from Goplaces: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
- Use the goplaces skill for this request.
- Help me with goplaces.
- Use when the user asks to query Google Places API New via the goplaces CLI for text search, place details, resolve, and reviews. Use for human-friendly place lookup or JSON output for scripts.
- Goplaces: provide an actionable result.
Negative
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use goplaces for unrelated requests.
- This request is outside goplaces scope.
- This is conceptual discussion only; no tool workflow is needed.
Runtime Prompt
- Current runtime prompt length: 812 characters.
- Runtime prompt is defined directly in
../goplaces.json.