Name: ringcentral
Rating: 55.2 (1 reviews)
Author: membranedev

ringcentral

RingCentral integration. Manage Users, Persons, Organizations, Leads, Deals, Projects and more. Use when the user wants to interact with RingCentral data.

Quality

63%

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

Quality

Content

66%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 a well-structured, largely executable guide for driving RingCentral via the Membrane CLI, with a strong connection-state workflow and a useful actions table. It loses points for vendor background prose Claude already knows and for lacking explicit validation checkpoints around the destructive delete-* actions.

Suggestions

Trim the introductory 'RingCentral is a cloud-based communication and collaboration platform...' paragraph; Claude already knows what RingCentral is.

Add an explicit validation/confirmation checkpoint before destructive actions (delete-message, delete-contact, delete-meeting), e.g. 'Confirm the target ID before running any delete-* action; deletes are irreversible.'

Tie a concrete action key from the table (e.g. send-sms) into the 'Running actions' example so the run command is end-to-end copy-pasteable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and a focused actions table, but it includes unnecessary background ('RingCentral is a cloud-based communication and collaboration platform...') explaining what the vendor is, which Claude does not need.	3 / 5
Actionability	Provides concrete, executable commands for install, auth, connection, search, run, and proxy flows, plus a flag table; only minor gaps remain (e.g. concrete <actionId> values tied to the table keys).	4 / 5
Workflow Clarity	The connection flow is well sequenced with a --wait poll loop and explicit handling of READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR states, though there is no validation checkpoint before running destructive actions like delete-message or delete-contact.	4 / 5
Progressive Disclosure	Clear sectioned overview (install, auth, connect, search, popular actions, proxy, best practices) with the large action catalog appropriately inlined as a table rather than a nested reference; no bundle files are present to reference.	4 / 5
	Total	15 / 20 Passed

Description

60%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 names the RingCentral domain and includes a 'Use when' trigger with several entity types, giving it solid completeness and distinctiveness. It is held back from higher scores by the generic 'Manage' verb and limited natural trigger-term coverage (no 'calls', 'SMS', 'Glip', 'API').

Suggestions

Replace the generic verb 'Manage' with several concrete actions users perform, e.g. 'Send SMS and Glip messages, list and create contacts, schedule meetings, and retrieve call logs.'

Expand trigger terms to natural user phrasings: 'Use when the user wants to send RingCentral SMS, manage Glip chats, look up call logs, or query the RingCentral API.'

Add file/format or synonym cues (e.g. 'RingCentral API', 'Glip', 'call logs') to improve trigger-term quality and reduce overlap with generic CRM skills.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete entity types ('Users, Persons, Organizations, Leads, Deals, Projects and more'), but the actions are generic ('Manage') rather than distinct specific verbs, so coverage is present but not comprehensive.	3 / 5
Completeness	It states both what ('Manage Users, Persons, Organizations, Leads, Deals, Projects and more') and when ('Use when the user wants to interact with RingCentral data'), satisfying both halves, though the trigger phrasing is fairly general.	4 / 5
Trigger Term Quality	It includes 'RingCentral data' and entity names as keywords, plus a 'Use when' clause, but it lacks common user phrasings like 'RingCentral API', 'SMS', 'calls', 'Glip', 'messages', or file-extension equivalents.	3 / 5
Distinctiveness Conflict Risk	The 'RingCentral' niche is distinct and clearly scoped to one vendor's data, with only minor overlap risk against other CRM/communication 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/ringcentral/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.