Name: munity
Rating: 52 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

munity

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

Quality

57%

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

Quality

Content

57%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 is a solid, executable guide to the Membrane/Munity CLI workflow with strong command coverage and good connection-state validation. Its main weaknesses are padded prose, a destructive-operations path lacking verification steps, and a monolithic structure with no bundle references.

Suggestions

Add a verification/confirm checkpoint before destructive proxy calls (POST/PUT/PATCH/DELETE) and before `membrane action run` on mutating actions, e.g. dry-run or read-then-write.

Trim explanatory prose such as the auth-plumbing and app-matching sentences so every token earns its place.

Fix the dangling "Step 2" and "1b" step labels so the sequence is unambiguous, or extract the connection state-machine and proxy reference into referenced files.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI documentation, but several prose passages — e.g. "so you can focus on the integration logic rather than auth plumbing" and the app-matching explanation — are over-explanation that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connection, action search/run, and proxying with a full flag table, with only minor gaps such as unsubstituted placeholders and a redundant "Popular actions" section.	4 / 5
Workflow Clarity	The connection setup has clear state-based validation and polling feedback loops, but the proxy and action-run paths support destructive HTTP methods and mutations with no verification step, which caps workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	No bundle files exist and the skill is a single ~140-line document; it is well-sectioned with headers, but content that could live in separate references (the proxy flag table, the detailed clientAction state machine) is inlined with no signaled external references.	3 / 5
	Total	13 / 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 successfully pairs a stated capability with an explicit use-when trigger anchored to a named product, but its action list is generic rather than concrete. Tightening "manage data, records, and automate workflows" into specific operations would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete actions, e.g. "List and create community members, posts, and records; run and automate Munity workflows."

Add natural trigger variations users would say, such as "Munity community", "Munity posts", or "query Munity records".

Keep the explicit "Use when..." clause but make the "what" clause list 2-3 specific, distinguishable operations.

Dimension	Reasoning	Score
Specificity	The description names the Munity domain but the actions listed — "Manage data, records, and automate workflows" — are generic verbs rather than concrete capabilities, fitting the anchor that names the domain with minimal or generic actions.	2 / 5
Completeness	It provides both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when the user wants to interact with Munity data" clause, but the "what" is generic rather than concrete, so it does not reach the level-5 anchor.	4 / 5
Trigger Term Quality	It includes the natural product keyword "Munity" and the phrase "Munity data" in the trigger, but lacks common variations or synonyms a user might say, matching the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named product "Munity" gives it a clear niche with minimal conflict risk, though the generic "manage data" phrasing leaves minor overlap with broad 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/munity/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.