Name: mocean-api
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mocean-api

Mocean API integration. Manage Organizations, Users, Filters. Use when the user wants to interact with Mocean API 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/mocean-api/SKILL.md

Quality

Content

75%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 highly actionable, with executable commands and a well-sequenced connection workflow that includes polling and state-based branching. Its main weaknesses are an unnecessarily padded intro and loosely labeled step references that slightly muddy navigation.

Suggestions

Trim the introductory paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing"; assume Claude knows what an SMS/communication API is.

Replace the informal "Step 1b"/"Step 2" references with a single explicit numbered sequence (1. Install, 2. Authenticate, 3. Connect, 4. Search & run) so the workflow is unambiguous.

Consider moving the detailed connection-state reference (clientAction.type values and polling rules) into a references file and keeping only the happy path inline, to tighten the overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but opens with padding ("Mocean API is a communication platform that allows developers to send and receive SMS messages... It's used by businesses and developers...") and includes throwaway phrases like "so you can focus on the integration logic rather than auth plumbing" that assume Claude lacks general knowledge.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands for every common case (install, login, connection ensure with --wait polling, action list/run with --input JSON, and a complete proxy flag table), covering the realistic workflow end to end.	5 / 5
Workflow Clarity	The install → login → connection ensure → poll-for-state → run-action sequence is clear with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll feedback loop, but the "Step 1b"/"Step 2" labels reference steps that are not formally numbered, creating a minor navigation gap.	4 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections (Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references and no bundle files to traverse; the only gap is that the verbose connection-state handling could arguably live in a reference file rather than inline.	4 / 5
	Total	16 / 20 Passed

Description

66%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 cleanly identifies a distinct niche and provides an explicit Use-when trigger, but its action vocabulary is generic ("Manage") and it omits the natural capability keywords (SMS, voice, verify) that users would actually invoke. Tightening the verb choices and adding capability synonyms would lift specificity and trigger quality.

Suggestions

Replace the generic verb "Manage" with concrete actions per resource, e.g. "Create and update Organizations, invite Users, configure Filters".

Add natural capability trigger terms such as SMS, voice calls, and phone verification so the description matches what users actually ask for.

Make the "when" clause more specific, e.g. "Use when the user wants to send SMS, make voice calls, or verify phone numbers via Mocean API."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Mocean API") and three concrete resource entities ("Organizations, Users, Filters"), but relies on the single generic verb "Manage" rather than enumerating specific actions, so coverage is not comprehensive.	3 / 5
Completeness	It states both what ("Manage Organizations, Users, Filters") and when ("Use when the user wants to interact with Mocean API data"), but the "when" clause is generic and could be more explicit about the specific use cases.	4 / 5
Trigger Term Quality	"Mocean API" and "interact with Mocean API data" are relevant keywords, but the description omits the natural capability terms a user would actually say (SMS, voice calls, verification, number lookup), missing common variations and synonyms.	3 / 5
Distinctiveness Conflict Risk	Targeting the specific Mocean platform forms a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/mocean-api/SKILL.md
Commit: f484c82

Reviewed: 6 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.