Name: rise
Rating: 64.8 (1 reviews)
Author: membranedev

rise

Rise integration. Manage Users, Organizations, Leads, Pipelines, Filters. Use when the user wants to interact with Rise data.

Quality

78%

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/rise/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.

A strong, command-driven integration skill: highly actionable CLI examples with a clear connection state machine and good section structure. It loses a little on conciseness to light framing prose and on workflow clarity to a missing explicit post-run failure checkpoint, and there are no separate reference files to offload detail.

Suggestions

Add an explicit validate-and-retry checkpoint after 'membrane action run' (e.g. check the output/error field, re-discover the action or adjust input if it fails) to lift workflow clarity toward 5.

Trim framing sentences like 'so you can focus on the integration logic rather than auth plumbing' that restate what the commands already show.

Consider moving the full proxy options table and detailed clientAction field reference into a separate reference file, with the body linking to it, to strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable commands and a tight best-practices list, but the overview paragraph and a few framing sentences (e.g. 'so you can focus on the integration logic rather than auth plumbing') add mild padding.	4 / 5
Actionability	It provides copy-paste-ready CLI commands with concrete flags for install, login, connection ensure, polling, action list/run, and proxy requests, plus a complete options table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with a state machine (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a polling loop, and action discovery-to-run is well ordered, though there is no explicit validation/retry checkpoint after a run fails.	4 / 5
Progressive Disclosure	Sections are well organized (Install, Authentication, Connecting, Searching, Popular actions, Best practices) and the body stays at overview depth, but there are no external reference files to offload bulk detail and a couple of inline lists could be split out.	4 / 5
	Total	17 / 20 Passed

Description

73%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.

A solid, third-person description that names the domain and concrete entities plus an explicit 'Use when' trigger. It is comprehensive enough to be distinctive and actionable, with only minor gains available from richer trigger synonyms and varied verbs.

Suggestions

Add natural trigger synonyms beyond 'Rise data' (e.g. 'Rise CRM', 'Rise leads', 'Rise users') so users phrase the need in more ways.

Vary the single 'Manage' verb with more specific actions per entity (e.g. 'Create and assign training, track learner progress, manage pipelines') to lift specificity from 4 to 5.

Keep the existing third-person voice and 'Use when' clause, which already satisfy the completeness and voice guidelines.

Dimension	Reasoning	Score
Specificity	Names the domain (Rise) and enumerates several concrete capabilities ('Manage Users, Organizations, Leads, Pipelines, Filters'), but the verbs are a single generic 'Manage' applied to a list rather than distinct actions, leaving minor gaps in coverage.	4 / 5
Completeness	It answers both 'what' (Rise integration managing Users/Organizations/Leads/Pipelines/Filters) and 'when' ('Use when the user wants to interact with Rise data'), with the 'when' explicit but only lightly specified.	4 / 5
Trigger Term Quality	The explicit trigger clause 'Use when the user wants to interact with Rise data' is natural and direct, but keyword coverage relies almost entirely on the brand name 'Rise' with limited synonyms or natural variation beyond 'interact with'.	4 / 5
Distinctiveness Conflict Risk	The Rise brand name is a strong, distinctive trigger with minimal overlap risk against unrelated skills, and the enumerated entities further scope it to a clear niche.	5 / 5
	Total	17 / 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/rise/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.