Name: openlayer
Rating: 60 (1 reviews)
Author: membranedev

openlayer

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

Quality

70%

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/openlayer/SKILL.md

Quality

Content

82%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 content is highly actionable, built around concrete, copy-paste-ready Membrane CLI commands, and the connection-state workflow includes genuine validation checkpoints and a retry loop. The main weaknesses are minor over-explanation in the intro and a loosely numbered overarching workflow with a dangling 'Step 2' reference.

Suggestions

Trim the opening paragraph explaining what OpenLayer/Openlayer is (Claude already knows the library) and remove the filler line 'When to use which actions: Use action names and parameters as needed.'

Number the end-to-end flow (1. Install, 2. Authenticate, 3. Connect, 4. Discover actions, 5. Run) and resolve the dangling 'Step 2' reference so the overarching workflow is as crisp as the connection sub-workflow.

De-duplicate the action-list command, which appears nearly verbatim in both 'Searching for actions' and 'Popular actions', to tighten the body further.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient, leading with executable commands and a compact proxy-flag table, but includes minor over-explanation Claude already knows (the opening 'Openlayer is a JavaScript library used for creating interactive web maps...' paragraph) and a filler line ('When to use which actions: Use action names and parameters as needed'), fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean 5.	4 / 5
Actionability	It provides copy-paste-ready, executable commands throughout — install, login (incl. headless completion), connection ensure/get with --wait, action list/run with --input JSON, and the proxy request with a full flag table — covering the common cases, matching the 'fully executable; copy-paste ready code or commands; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with explicit state checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-after-user-action feedback loop, but the broader install→auth→connect→search→run flow is not numbered and references an undefined 'Step 2', leaving minor gaps, matching 'clear sequence with most checkpoints present; minor validation gaps' rather than 5.	4 / 5
Progressive Disclosure	With no bundle files present, all content is inline but organized into clear sections (Overview, Working with Openlayer, Popular actions, Best practices) with well-signaled subsections; at ~140 lines it is slightly long for a single file with no external references, fitting 'good structure; most content appropriately placed; minor organization gaps' rather than the 5 reserved for a concise overview with one-level-deep references.	4 / 5
	Total	17 / 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 correctly includes an explicit 'Use when' trigger and names the product, giving it solid completeness and distinctiveness, but its capability list is generic boilerplate rather than concrete Openlayer-specific actions. Tightening the 'what' with real Openlayer use cases would lift specificity.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Openlayer-specific actions (e.g., 'create and query records, inspect traces and datasets, run evaluations') so the capability list is specific rather than templated.

Expand the trigger clause with natural variations users would actually say, e.g. 'Use when the user wants to inspect Openlayer traces, manage datasets, or automate evaluation workflows.'

Keep the named 'Openlayer' trigger but add a synonym or file/URL cue to reduce overlap with other Membrane integration skills that share the same boilerplate.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Openlayer integration') but the actions listed ('Manage data, records, and automate workflows') are minimal and generic rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Openlayer data') are present and explicit, though the 'when' clause is generic; this matches the 'has both what and when; when could be more specific' anchor rather than 3 (which requires a missing/weak when) or 5 (which requires concrete trigger phrases).	4 / 5
Trigger Term Quality	It includes the relevant product keyword 'Openlayer' in a natural trigger phrase ('interact with Openlayer data'), but offers only that single term with no synonyms or variations, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named product 'Openlayer' gives a clear niche with minimal conflict risk, but the templated 'Manage data, records, and automate workflows' phrasing is shared across many Membrane integration skills, leaving minor overlap risk, matching 'mostly distinct; minor overlap risk with closely related skills'.	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/openlayer/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.