Name: ringba
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ringba

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

Quality

74%

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/ringba/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 body is highly actionable with executable commands and a well-structured connection workflow including error-recovery loops, held back only by minor redundancy, an inconsistent step numbering scheme, and a monolithic single-file structure.

Suggestions

Remove the duplicated `membrane action list` command in "Popular actions" or fold that section into "Searching for actions".

Fix the connection step numbering (label "Step 1" and the referenced "Step 2") so the workflow is unambiguous.

Move the clientAction field reference and the proxy flag table into a separate REFERENCE.md linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient concrete commands with only minor over-explanation (the opening marketing-style description of Ringba and a duplicated `action list` command across "Searching for actions" and "Popular actions"), so it sits above the midpoint but not fully lean.	4 / 5
Actionability	Provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure/get --wait, action list/run, request with a complete flag table), covering the common cases with explicit placeholders.	5 / 5
Workflow Clarity	The connection workflow has a clear state-driven sequence with polling and error-recovery feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but step numbering is inconsistent (a "1b" with no labeled "Step 1"/"Step 2"), leaving minor gaps.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references, but the doc is a single >50-line file with substantial inline API reference (clientAction fields, proxy flag table) that could be split into reference files.	4 / 5
	Total	17 / 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 is distinct and includes both a what and a when, but its action vocabulary is generic and the trigger phrasing is narrow, missing concrete verbs and natural synonyms.

Suggestions

Replace generic verbs with concrete Ringba actions (e.g., "query call logs, manage campaigns and numbers, pull reports") to raise specificity.

Broaden the trigger with natural user phrases and entities (e.g., "Use when the user wants to track calls, manage Ringba campaigns/numbers, or pull call analytics").

Add concrete trigger nouns like call tracking, campaigns, publishers, or invoices that a user would actually mention.

Dimension	Reasoning	Score
Specificity	Names the domain (Ringba) and a few actions — "Manage data, records, and automate workflows" — but the actions are generic rather than concrete (cf. "extract text, fill forms"), so it sits at the domain-plus-vague-actions anchor rather than clearly above.	3 / 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 Ringba data"), but the "when" is fairly generic and could be more specific.	4 / 5
Trigger Term Quality	The natural term "Ringba" is present in the trigger clause, but the phrasing "interact with Ringba data" lacks common variations, synonyms, or concrete trigger nouns users would actually say.	3 / 5
Distinctiveness Conflict Risk	Ringba is a specific named platform and the trigger is scoped to it, giving a clear niche with minimal overlap risk against 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/ringba/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.