Name: opteo
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

opteo

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

Quality

59%

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

Quality

Content

61%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 well-structured, mostly executable guide to driving Opteo via the Membrane CLI with clear command examples and a sensible connection-state workflow. Its main gaps are absent validation/verification checkpoints around mutating operations and some padded explanatory prose.

Suggestions

Add a validation step to mutating workflows: after `membrane action run` or `membrane request` with POST/PUT/DELETE, verify the change (e.g. re-query the affected resource or check the response state) and retry on error.

Trim inferable prose such as the explanation that Membrane handles auth/refresh and the duplicate action-discovery command under 'Popular actions', keeping only the command plus a one-line note.

Provide at least one complete worked proxy example with real --json/-d values and show how to read the result from the `output` field, so the proxy path is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-oriented, but it restates things Claude can infer (e.g. explaining that Membrane "handles authentication and credentials refresh automatically" and the verbose "Popular actions" discovery line that duplicates the earlier action-list command), matching the score-3 anchor of mostly efficient with some tightening possible; it is not a 4 because several explanatory sentences pad sections rather than earning their tokens.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands across install, login, connection, action search/run, and proxy requests with flags documented, matching the score-4 "mostly executable guidance with minor gaps" anchor; it is not a 5 because some examples leave placeholders (CONNECTION_ID, <actionId>, <code>) and the proxy section lacks a complete worked example with --data/--json.	4 / 5
Workflow Clarity	The connection setup flow is sequenced with state-handling branches, but for operations that can mutate ads/campaigns (action run, proxy POST/PUT/DELETE) there are no validation or verification checkpoints before/after execution, so per the feedback-loop guidance destructive/batch operations without validation cap this dimension at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Overview, Working with Opteo, Popular actions, Best practices) with no bundle files present and no deep nested references, so per the simple-skill guidance it has good structure with only minor organization gaps (e.g. the 1b sub-step numbering is slightly inconsistent with the rest of the flow), fitting the score-4 anchor.	4 / 5
	Total	14 / 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 names Opteo and includes an explicit 'Use when' trigger, satisfying the what/when requirement at a solid level. Its weakness is generic, non-Opteo-specific action language and thin trigger-term coverage with no synonyms or task-oriented phrases.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Opteo actions, e.g. "Manage Google Ads campaigns, ad groups, keywords, and ads; monitor performance alerts and generate reports".

Expand the trigger clause to include natural synonyms and task phrases, e.g. "Use when the user wants to manage Opteo/GitHub Ads campaigns, check performance alerts, or run reports".

Adopt third-person capability phrasing and keep the description to one tight sentence plus one trigger sentence to avoid padding.

Dimension	Reasoning	Score
Specificity	It names the domain ("Manage data, records, and automate workflows") but the actions are generic abstractions like "manage" and "automate workflows" with no concrete Opteo-specific capabilities, matching the score-2 anchor "Names the domain but actions are minimal or generic"; it does not reach score 3 because there is not even one concrete, Opteo-specific action enumerated.	2 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Opteo data"), matching the score-4 anchor where both are present but the when could be more specific; it is not a 5 because the trigger phrase is a single generic clause rather than concrete enumerated triggers.	4 / 5
Trigger Term Quality	"interact with Opteo data" supplies the key trigger noun a user would say, but there are no synonyms, common variations, or related task phrases (e.g. ads, campaigns, reports, alerts), fitting the score-3 anchor of relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Opteo makes it largely distinct from other skills with minimal overlap risk, matching the score-4 "mostly distinct; minor overlap risk" anchor; it is not a 5 only because the generic "manage data, records, automate workflows" wording could conceivably overlap with broader data-management 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/opteo/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.