Name: rock-rms
Rating: 45.6 (1 reviews)
Author: membranedev

rock-rms

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

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/rock-rms/SKILL.md

Quality

Content

38%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 Membrane CLI usage section is executable and reasonably well-structured, but it is buried under an enormous, auto-generated entity list that is mostly noise and should not live in SKILL.md. The skill also lacks verification steps for destructive data operations.

Suggestions

Remove the ~370-line entity list from SKILL.md (or move genuine entities to a references/ file); the duplicated 'Workflow...View View View' entries are pure padding.

Add a validate/verify checkpoint after running actions or proxy mutations, e.g. re-query the record to confirm the change before reporting success.

Replace 'Use action names and parameters as needed.' with one or two concrete Rock RMS action examples showing real input JSON and expected output.

Dimension	Reasoning	Score
Conciseness	The body is dominated by a ~370-line entity list riddled with nonsensical duplicated entries (e.g. "Workflow Workflow Trigger Workflow Trigger... View View View View View"), which is severely padded noise; the intro also explains what Rock RMS is. This matches the 'severely verbose; heavily padded' anchor.	1 / 5
Actionability	The CLI section provides concrete, executable, copy-paste commands (install, login, connection ensure, action list/run, request) plus a flags table, matching the 'mostly executable guidance with minor gaps' anchor. It is not 5 because Rock RMS-specific action examples use placeholders and the entity list adds no actionable guidance.	4 / 5
Workflow Clarity	The connection setup is well-sequenced with polling and state feedback loops, but the core data-operation workflow (action run and proxy requests that can perform PUT/PATCH/DELETE) lacks any validate-then-verify step. Per the destructive/batch feedback-loop cap, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	No bundle files exist and the massive entity reference is inlined directly in SKILL.md rather than split into a separate reference file, with no file-based navigation. This matches the anchor for content that clearly belongs in separate files being inlined.	2 / 5
	Total	10 / 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 cleanly answers both what and when with a distinct Rock RMS trigger, but its capability language is generic and trigger-term coverage is narrow. Strengthening it with concrete actions and more natural synonyms would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Rock RMS capabilities, e.g. "query person and group records, run workflows, manage financial transactions".

Expand trigger terms with natural synonyms users say, such as "church management", "ChMS", "Rock RMS records", or specific entity names.

Tighten the 'when' clause to name concrete scenarios, e.g. "Use when the user wants to query, create, or update Rock RMS records or run Rock RMS workflows."

Dimension	Reasoning	Score
Specificity	The description names the Rock RMS domain but its actions ("Manage data, records, and automate workflows") are generic and abstract rather than concrete, matching the anchor for naming the domain with minimal/generic actions. It does not reach 3 because no concrete capabilities (e.g. specific CRUD or workflow operations) are listed.	2 / 5
Completeness	It states both what it does ("Rock RMS integration. Manage data, records, and automate workflows.") and when to use it ("Use when the user wants to interact with Rock RMS data."), matching the anchor for both present with the 'when' reasonably explicit. It is not 5 because the 'what' is generic and trigger phrases are limited.	4 / 5
Trigger Term Quality	It includes natural terms users would say ("Rock RMS", "Rock RMS data", "records", "workflows") but misses common variations, synonyms, or file/record-type extensions. This fits the anchor for some relevant keywords with missing variations rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	"Rock RMS" is a clear, specific niche trigger giving it low conflict risk, but the broad "Manage data, records, and automate workflows" phrasing creates minor overlap risk with generic CRM/data skills, matching the 'mostly distinct; minor overlap' anchor rather than the fully distinct 5.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (521 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/rock-rms/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.