CtrlK
BlogDocsLog inGet started
Tessl Logo

goplaces

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.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary lean CLI reference: tightly organized, fully executable, and free of padding. It adds only what Claude would not already know and is immediately actionable.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation; every line (Config, Common commands, Notes) provides only operationally useful specifics Claude would not already know.

3 / 3

Actionability

Commands like `goplaces search "coffee" --open-now --min-rating 4 --limit 5` and `goplaces details <place_id> --reviews` are concrete, executable, and copy-paste ready with real flags and arguments.

3 / 3

Workflow Clarity

This is a simple single-purpose skill where the single action (running goplaces commands) is unambiguous, so workflow clarity scores full per the simple-skills allowance; no destructive or batch operations require validation checkpoints.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, the body is organized into clearly labeled sections (Install, Config, Common commands, Notes), satisfying progressive disclosure for a simple skill.

3 / 3

Total

12

/

12

Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description with an explicit trigger clause and concrete capabilities. It would benefit from broader natural-language trigger terms to match how users actually phrase location queries.

Suggestions

Add common natural trigger terms such as "nearby", "find places near me", or "local search" so the description matches real user phrasings.

Mention concrete query intents like "find restaurants/coffee/shops" to widen trigger coverage beyond "place lookup".

DimensionReasoningScore

Specificity

"text search, place details, resolve, and reviews" plus "human-friendly place lookup or JSON output for scripts" lists multiple concrete, distinct actions rather than vague language.

3 / 3

Completeness

It states what the skill does (query the Places API via the goplaces CLI for named tasks) and gives an explicit "Use for..." trigger clause covering when to invoke it.

3 / 3

Trigger Term Quality

"place lookup", "Google Places API", and "JSON output for scripts" are relevant, but common natural phrasings like "nearby", "find places near me", or "local search" are missing.

2 / 3

Distinctiveness Conflict Risk

The Google Places API (New) / goplaces CLI niche is specific and distinct, making accidental triggering by unrelated skills unlikely.

3 / 3

Total

11

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
Bitterbot-AI/bitterbot-desktop
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.