Name: highrise
Rating: 58.4 (1 reviews)
Author: membranedev

highrise

Highrise integration. Manage Persons, Organizations, Deals, Leads, Cases, Tasks and more. Use when the user wants to interact with Highrise data.

Quality

67%

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/highrise/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 highly actionable with concrete Membrane CLI commands and a solid connection workflow including state-based feedback loops. Its main weaknesses are mild verbosity explaining CRM basics, an undefined "Step 2" reference, and the absence of validation guidance for destructive delete operations.

Suggestions

Remove or trim the opening CRM explainer ("Highrise is a CRM...It helps small businesses keep track of...") since Claude already knows this, improving token efficiency.

Add a validation/confirmation checkpoint before destructive actions (e.g. "Before running delete-* actions, confirm the target ID with the user") to lift workflow clarity above the destructive-operations cap.

Fix the dangling "Step 2" reference by either numbering the workflow steps consistently (Step 1, 1b, Step 2) or replacing it with the actual section name ("Searching for actions").

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation Claude already knows ("Highrise is a CRM (Customer Relationship Management) tool. It helps small businesses keep track of leads, contacts, tasks...") and some padded prose, fitting the score-3 anchor of mostly efficient with some over-explanation.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (npm install, membrane login, connection ensure, action list/run, request) plus a popular-actions table with keys, giving mostly executable guidance with minor gaps such as the undefined "Step 2" reference.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with polling checkpoints and state feedback loops (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive operations (delete-person, delete-company) are listed without any validation/verification guidance, which caps workflow clarity at 3 per the destructive-operations rule; step numbering is also inconsistent ("Step 2" is never defined).	3 / 5
Progressive Disclosure	The body is well-organized into clear sections (Overview, Working with Highrise, Authentication, Connecting, Searching, Popular actions, Proxy requests, Best practices) with no nested references and no bundle files needed, matching the score-4 anchor of good structure with minor organization gaps such as the large inlined actions table.	4 / 5
	Total	14 / 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.

The description cleanly states what the skill does and when to use it with a specific named product, but leans on the generic verb "Manage" rather than concrete actions and a somewhat generic trigger clause. It is solid but could be sharper with enumerated action verbs and scenario-based triggers.

Suggestions

Replace the single verb "Manage" with concrete actions (e.g. "Create, list, update, and delete Persons, Organizations, Deals, Leads, Cases, and Tasks") to lift specificity.

Expand the "Use when" clause with concrete trigger scenarios (e.g. "Use when the user wants to list Highrise contacts, create a deal, or update a task") to reach full completeness.

Dimension	Reasoning	Score
Specificity	The phrase "Manage Persons, Organizations, Deals, Leads, Cases, Tasks and more" names the domain and many entity types, but the single generic verb "Manage" applied to all of them is not a comprehensive set of concrete actions, matching the score-3 anchor (names domain and 1-2 concrete actions).	3 / 5
Completeness	It has both a clear "what" ("Manage Persons, Organizations, Deals...") and an explicit "when" ("Use when the user wants to interact with Highrise data"), but the trigger is generic rather than enumerating concrete scenarios, so it sits at score 4 rather than 5.	4 / 5
Trigger Term Quality	Natural terms like "Highrise", "Persons, Organizations, Deals, Leads, Cases, Tasks", and "interact with Highrise data" give good keyword coverage a user would actually say, with only minor synonyms (e.g. "contacts", "companies") missing, fitting the score-4 anchor.	4 / 5
Distinctiveness Conflict Risk	"Highrise integration" names a specific CRM product with distinct triggers tied to that product, giving a clear niche with minimal conflict risk, matching the score-5 anchor.	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/highrise/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.