Name: here
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

here

HERE integration. Manage data, records, and automate workflows. Use when the user wants to interact with HERE data.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/here/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

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

The body is a well-structured, actionable CLI guide with concrete commands and good connection-state feedback loops. Its main weaknesses are a padded intro paragraph and inconsistent step numbering that slightly muddle the workflow sequence.

Suggestions

Trim the introductory paragraph to remove over-explanation of what HERE is and the 'auth plumbing' commentary.

Fix the step numbering so 'skip to Step 2' resolves to an actual labeled Step 2, and renumber the lone '1b' subsection consistently.

Standardize command invocation (choose either 'membrane' or 'npx @membranehq/cli@latest') to avoid confusing the reader.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and a compact flag table, but the intro paragraph over-explains HERE ('Think of it as an alternative to Google Maps Platform...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' add padding, fitting 'Mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action run, request) plus a full proxy flags table, but minor gaps like the inconsistent 'membrane' vs 'npx @membranehq/cli' invocation and placeholder CONNECTION_ID keep it just below fully executable, matching 'Mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The install → authenticate → connect → search → run sequence is clear, and the connection state handling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with re-poll feedback) provides explicit checkpoints, but the step numbering is inconsistent ('skip to Step 2' with no Step 2 header; a lone '1b' subsection), fitting 'Clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no broken or nested references, and as a single CLI-usage file it has no need for external bundle files; it sits just below the ideal because some content like the proxy flag table could live in a separate reference, matching 'Good structure; most content is appropriately placed'.	4 / 5
	Total	15 / 20 Passed

Description

57%Weight 40%Scale 1-5

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

The description answers both what and when with an explicit trigger clause, but its capability wording is generic rather than concrete and it lacks natural synonyms like 'maps' or 'location'. It is distinct thanks to the HERE brand yet could be sharper.

Suggestions

Replace generic verbs with concrete HERE capabilities, e.g. 'Search routes, manage projects, query location records, and automate HERE workflows'.

Add natural trigger synonyms users actually say, such as 'HERE maps', 'location data', 'routing', or 'geocoding'.

Tighten the 'Use when' clause to list specific intents, e.g. 'Use when the user wants to query HERE maps, routing, or location data'.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the HERE domain and lists several actions, but the actions are generic ('manage', 'automate') rather than concrete capabilities, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with HERE data'), but the 'what' is generic and the 'when' could be more specific, matching 'Has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	It repeats 'HERE data' and 'HERE integration' as triggers, but misses common natural synonyms users would say such as 'HERE maps', 'location data', 'routing', or 'geocoding', fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The HERE platform brand gives it a clear niche and distinct triggers ('interact with HERE data'), but the generic 'manage data, records, automate workflows' wording creates minor overlap risk with other integration skills, fitting 'Mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/here/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.