Name: chmeetings
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

chmeetings

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

Quality

64%

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

Quality

Content

65%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 skill body is highly actionable with copy-paste-ready CLI commands and a clear connection workflow, but it is let down by inlined reference material that belongs in a separate file and by the absence of validation/verification guidance around destructive and batch actions.

Suggestions

Add explicit validation/verification steps for destructive and batch actions (e.g. confirm entity exists before delete, verify counts after batch creation) to lift workflow clarity above the cap.

Move the full popular-actions table and proxy-flag reference into a separate reference file (e.g. ACTIONS.md) and link to it, keeping only the most-used examples inline.

Trim redundant explanatory prose around connection states and the Membrane-auth pitch to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the lengthy action-table (20 rows of popular actions) and verbose connection-state explanations add padding that could be trimmed or moved to a reference file; it does not reach the lean score-5 anchor.	3 / 5
Actionability	Commands are copy-paste ready and complete (login, connection ensure/get with --wait, action list/run with JSON input, request proxy flags), and the popular-actions table plus proxy options cover the common cases exactly as the score-5 anchor describes.	5 / 5
Workflow Clarity	The connection sequence is well laid out (ensure -> wait/poll for state -> READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive and batch operations (delete-family, delete-person, create-contribution) appear in the action table with no validation or verification checkpoint before running, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	There is section structure and no bundle files are referenced, but content that would benefit from a separate file (the 20-row popular-actions catalog, full proxy-flag reference) is inlined rather than split out, matching the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

63%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, anchored to a specific product name that keeps it distinct. Its main weakness is trigger-term breadth: it relies on the product name alone rather than enumerating natural phrases and synonyms users would say.

Suggestions

Expand the trigger clause with natural user phrasing and synonyms, e.g. 'Use when the user wants to manage church members, attendance, events, giving, or groups in ChMeetings'.

List a few more concrete capabilities (e.g. track attendance, manage giving/pledges, organize groups and events) to lift specificity toward comprehensive coverage.

Keep the third-person voice but add common surface terms like 'church management' or 'ChMeetings API' that users actually say.

Dimension	Reasoning	Score
Specificity	Names the domain (ChMeetings) plus several concrete actions ('Manage data, records, and automate workflows'), with only minor coverage gaps; it stops short of the score-5 anchor's comprehensive enumeration of multiple specific operations.	4 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with ChMeetings data) are present, but the 'when' clause is somewhat generic and could be more specific with concrete trigger phrases, matching the score-4 anchor.	4 / 5
Trigger Term Quality	The trigger phrasing 'Use when the user wants to interact with ChMeetings data' uses the product name as the main keyword but lacks natural synonyms and concrete surface terms users would say; this sits at the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill explicitly to the ChMeetings product name gives it a clear niche with minimal conflict risk against unrelated skills; minor overlap risk remains only with closely related CRM/church-management tools, fitting the score-4 anchor better than the more generic score-3.	4 / 5
	Total	15 / 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/chmeetings/SKILL.md
Commit: f484c82

Reviewed: 3 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.