Name: reapit
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

reapit

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

Quality

60%

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

Quality

Content

63%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 delivers highly actionable CLI guidance with a well-checkpointed connection workflow, but it carries a redundant entity wall and no reference-file split. Tightening redundancy and moving the entity catalog to a reference file would improve it most.

Suggestions

Move the 40-item entity list into a separate reference file (e.g. references/entities.md) and link to it, keeping only the most common entities inline.

De-duplicate the 'Searching for actions' and 'Popular actions' sections, which both demonstrate `membrane action list --intent`.

Add a validation step after running actions (e.g. check the `output` field and handle error states) and resolve the undefined 'Step 2' reference in the connection flow.

Dimension	Reasoning	Score
Conciseness	The CLI command sections are efficient, but the ~40-item entity list is a low-value wall of bare terms and the 'Searching for actions' and 'Popular actions' sections repeat the same `membrane action list` command. It is not 4 because these padded/redundant sections are noticeable rather than minor.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands across install, auth, connection, action search/run, and proxy, plus a flag table. It is not 5 because of CONNECTION_ID placeholders and the vague directive 'Use action names and parameters as needed'.	4 / 5
Workflow Clarity	The connection workflow has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) with a poll-retry feedback loop. It is not 5 because 'skip to Step 2' references an undefined step and action-run results are never validated.	4 / 5
Progressive Disclosure	Section headers are clear, but the bulky entity list is inlined in SKILL.md and there are no external reference files, so content that could be split out is inline. It is not 4 because, at over 50 lines, the simple-skill exception does not apply and organization gaps are more than minor.	3 / 5
	Total	14 / 20 Passed

Description

57%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 includes an explicit 'Use when' trigger and a clearly distinct product name, but its capability list is generic and its keyword coverage is thin. Strengthening the concrete actions and adding natural domain synonyms would raise it most.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Reapit operations, e.g. 'Search and update properties, manage applicants and appointments, create offers and tenancies'.

Add natural trigger synonyms users say beyond 'Reapit', such as estate agency, property listings, landlords, or viewings.

Tighten the 'when' clause with concrete triggers, e.g. 'Use when the user wants to query or update Reapit property, applicant, or tenancy records.'

Dimension	Reasoning	Score
Specificity	The description names the Reapit domain but its actions ('Manage data, records, and automate workflows') are generic and abstract rather than concrete, matching the anchor for minimal/generic actions. It does not reach 3 because no specific operations (e.g. 'list properties', 'create appointments') are named.	2 / 5
Completeness	It has both a 'what' (manage data, records, automate workflows) and an explicit 'Use when the user wants to interact with Reapit data' trigger clause. It is not 5 because the 'what' is vague and the 'when' lacks concrete trigger phrases beyond 'Reapit data'.	4 / 5
Trigger Term Quality	The only natural keyword is 'Reapit' / 'Reapit data', which is relevant but misses common variations users might say such as estate agency, property, or real estate. It is not 4 because keyword coverage is thin rather than just missing a few terms.	3 / 5
Distinctiveness Conflict Risk	'Reapit' is a uniquely named product with a distinct trigger, giving mostly distinct coverage with minimal conflict risk. It is not 5 because the generic 'manage data, records, automate workflows' phrasing introduces minor overlap with general data skills.	4 / 5
	Total	13 / 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/reapit/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.