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

Blog Docs Log in Get started

edapp

EdApp integration. Manage Courses, Users, Groups, Announcements. Use when the user wants to interact with EdApp 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/edapp/SKILL.md

Quality

Content

68%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 well-structured, actionable guide to driving EdApp via the Membrane CLI with real commands and a useful connection-state workflow. Its main weakness is the absence of validation/verification steps for the destructive actions it exposes.

Suggestions

Add a verification step before destructive actions, e.g. "Before delete-user, run get-user to confirm the ID, then re-run after to verify removal".

Trim the marketing intro ("mobile-first microlearning platform... engaging lessons") and filler lines like "Use action names and parameters as needed".

Fix the step numbering inconsistency (a "Step 2" is referenced but no Step 1/Step 2 headers exist; the section is labeled "1b").

Dimension	Reasoning	Score
Conciseness	The body is largely tight CLI reference material with copy-paste commands, though minor padding exists (the marketing-flavored intro and filler like "Use action names and parameters as needed") that could be trimmed.	4 / 5
Actionability	It provides concrete, executable Membrane CLI commands (install, login, connection ensure, action list/run, request) plus a flag table and an action key reference; minor gaps are the placeholder values (CONNECTION_ID, <actionId>, QUERY) the user must fill in.	4 / 5
Workflow Clarity	The connect-and-poll sequence is well laid out with a READY/CLIENT_ACTION_REQUIRED re-poll feedback loop, but the skill surfaces destructive actions (delete-user, delete-user-group, delete-webhook) with no validation or verification guidance before running them, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is organized into clear sections (overview, connecting, searching, popular actions, running, proxy, best practices) with no nested references; the 20-row action table is borderline inline reference material but reasonable to keep in a single-file skill.	4 / 5
	Total	15 / 20 Passed

Description

66%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 clearly identifies the EdApp niche and includes an explicit 'Use when' clause, answering both what and when. It could be strengthened by replacing the generic "Manage" with concrete action verbs and adding natural trigger synonyms.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create, list, update, and delete Courses, Users, and Groups".

Expand the trigger clause with natural phrasings users would say, e.g. "Use when the user wants to manage EdApp courses, users, groups, or send announcements".

Align the entity list with the body (the body lists Notification/Reward/Certificate rather than Announcements).

Dimension	Reasoning	Score
Specificity	Names the EdApp domain and several managed entities ("Courses, Users, Groups, Announcements") but relies on a single generic verb "Manage" rather than distinct concrete actions (e.g. create/list/delete), so it sits at the 1-2-actions/comprehensive boundary.	3 / 5
Completeness	It explicitly states both what ("EdApp integration. Manage Courses, Users, Groups, Announcements") and when ("Use when the user wants to interact with EdApp data"), but the 'when' trigger could be richer with concrete synonyms to reach the top anchor.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with EdApp data" surfaces the key term EdApp plus entity nouns, but the phrasing is somewhat abstract and misses common natural variations a user might say.	3 / 5
Distinctiveness Conflict Risk	"EdApp integration" targets a specific named application with a distinctive trigger, giving it a clear niche and minimal overlap risk with other skills.	5 / 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/edapp/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.