Name: opn
Rating: 56.8 (1 reviews)
Author: membranedev

opn

OPN integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with OPN data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/opn/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 content is a solid, mostly executable CLI integration guide with a well-validated connection workflow and clean section structure. Its main weaknesses are residual marketing prose, an inconsistent CLI invocation convention, and absent verification guidance for the action/proxy steps.

Suggestions

Delete the marketing intro sentence ("It's used by marketing teams...improve ROI") and trim phrases like "so you can focus on the integration logic rather than auth plumbing".

Standardize on one invocation form (either bare `membrane` or `npx @membranehq/cli@latest`) throughout, or state once that they are interchangeable.

Add a brief verification/inspection step after running actions or proxy requests (e.g., check the `output`/status fields and handle non-2xx responses) to close the workflow loop on potentially destructive calls.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and lean, but retains marketing-style padding ("It's used by marketing teams and advertising agencies to streamline their workflow, track performance, and improve ROI") and phrases like "so you can focus on the integration logic rather than auth plumbing" that Claude does not need.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, auth, connect, search, run, and proxy with a flags table, but invocation is inconsistent ("membrane" vs "npx @membranehq/cli@latest") and the action-run examples rely on unpopulated placeholders.	4 / 5
Workflow Clarity	The connection setup is a clearly sequenced flow with explicit validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED states) and polling feedback loops for error recovery, though the referenced "Step 2" is never labeled and the action/proxy sections lack verification steps.	4 / 5
Progressive Disclosure	No bundle files exist, so all content lives in a single well-sectioned SKILL.md with clear headers and no nested references; it is over 50 lines with some redundancy ("Popular actions" overlaps "Searching for actions") keeping it out of the top band.	4 / 5
	Total	15 / 20 Passed

Description

62%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 is functional and brand-distinct with both a what and a when clause, but it relies on a single generic action verb and a generic trigger phrase. Tightening the trigger and naming concrete operations would lift it into the top band.

Suggestions

Replace the generic verb "Manage" with concrete operations (e.g., "List, create, update, and delete Organizations, Pipelines, Users, Goals, and Filters").

Expand the trigger clause with concrete phrases users would say, e.g. "Use when the user wants to query or update OPN data, list OPN pipelines, or manage OPN users and goals."

Add a natural synonym or file/URL marker (e.g. the opn.ooo domain) so the trigger matches how users actually refer to the platform.

Dimension	Reasoning	Score
Specificity	The description names the OPN domain and lists five concrete objects ("Organizations, Pipelines, Users, Goals, Filters"), but the only action verb is the generic "Manage", so actions remain non-specific rather than comprehensive.	3 / 5
Completeness	Both a clear "what" ("Manage Organizations, Pipelines, Users, Goals, Filters") and an explicit "when" ("Use when the user wants to interact with OPN data") are present, though the trigger clause is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces the brand keyword "OPN" and a list of entity names, plus the trigger "Use when the user wants to interact with OPN data", but lacks natural synonyms or variations a user might actually say beyond the brand name.	3 / 5
Distinctiveness Conflict Risk	"OPN integration" carves out a distinct brand niche with low conflict risk, but the generic entity names (Users, Organizations, Filters) create minor overlap potential with other CRUD-style skills.	4 / 5
	Total	14 / 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/opn/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.