Name: ringover
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

ringover

Ringover integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with Ringover data.

Quality

66%

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/ringover/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 actionable and well-structured, with strong CLI command coverage and a clear connection-state workflow. Weaknesses are repeated action-discovery commands, a boilerplate intro, and missing validation/feedback steps for destructive proxy and action operations.

Suggestions

Add a validation/verification step after running actions and proxy requests (e.g., re-query the affected resource or check the response status) to support destructive and batch operations.

De-duplicate the `action list --intent=QUERY` instruction — define it once and reference it, rather than repeating the full command in three places.

Trim the opening paragraph describing what Ringover is, since Claude can infer this, and lead directly with the working-with-Ringover workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable CLI commands, but repeats the `action list --intent=QUERY` command across "Searching for actions", "Popular actions", and the "Discover before you build" best practice, and opens with a boilerplate description of what Ringover is that Claude could infer.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (connection ensure, action run with JSON input, request with a full flags table), with only minor gaps such as the unfilled CONNECTION_ID placeholder and no complete end-to-end worked example.	4 / 5
Workflow Clarity	The connection setup has a clear state-machine with polling and error states (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the action-execution and proxy paths (which support destructive methods like DELETE/PUT) lack validation or verification checkpoints, triggering the destructive-operation cap at 3.	3 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and no nested references; structure is good with only minor organization gaps such as the inline proxy-flags table.	4 / 5
	Total	14 / 20 Passed

Description

71%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 clearly identifies the product and enumerates concrete data entities, and includes an explicit "Use when" trigger. It is held back slightly by a generic verb, limited trigger-term synonyms, and a fairly broad trigger condition.

Suggestions

Replace the generic verb "Manage" with a few concrete actions (e.g., "Create, update, and query Persons, Organizations, Deals, Leads, Activities, and Notes").

Broaden trigger terms to natural synonyms users say, such as "Ringover contacts, calls, SMS, conversations, or deals".

Tighten the "Use when" clause to a more specific trigger, e.g. "Use when the user wants to query or update Ringover CRM data."

Dimension	Reasoning	Score
Specificity	Lists several concrete entities to manage ("Persons, Organizations, Deals, Leads, Activities, Notes and more"), giving broad coverage, though the verb "Manage" is generic rather than enumerating distinct actions.	4 / 5
Completeness	Explicitly answers both what ("Manage Persons, Organizations, Deals, Leads, Activities, Notes") and when ("Use when the user wants to interact with Ringover data"), with the trigger being explicit but somewhat generic.	4 / 5
Trigger Term Quality	Includes the natural phrase "interact with Ringover data" but lacks common synonyms or variations a user might say (contacts, calls, SMS, deals), so keyword coverage is only partial.	3 / 5
Distinctiveness Conflict Risk	Names a specific product (Ringover), creating a clear niche with distinct triggers and minimal risk of overlapping with unrelated skills.	5 / 5
	Total	16 / 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/ringover/SKILL.md
Commit: f484c82

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