Name: edusign
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

edusign

Edusign integration. Manage Documents, Templates, Users, Groups. Use when the user wants to interact with Edusign data.

Quality

66%

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

Quality

Content

61%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 strong executable command coverage and a useful actions table within a well-sectioned structure, but it is held back by unnecessary background prose, templated run examples, and a lack of validation checkpoints for destructive data operations.

Suggestions

Trim the opening background paragraph about what Edusign is and the auth-plumbing commentary; lead directly with the install/connect workflow to improve conciseness.

Add a concrete end-to-end run example using a real action key and real input (e.g. `membrane action run create-student --connectionId=... --input '{"firstName":"Ada"}'`), and document how to read the `output` field for that case.

Insert a validation/verification step before destructive actions (e.g. run `action list` to confirm the right action, then verify the returned `output` state after create/update/delete) to lift workflow clarity past the destructive/batch cap.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Edusign is a platform for creating and managing digital signatures and workflows...") explains background Claude does not need, and prose like "so you can focus on the integration logic rather than auth plumbing" is padding. The bulk is efficient command reference, so it sits at anchor 3: mostly efficient with some unnecessary explanation.	3 / 5
Actionability	Commands are concrete and executable throughout (install, login, connection ensure/get, action list/run, request) and the Popular actions table gives real action keys. However the run examples are templated with <actionId> and {"key":"value"} rather than a copy-paste-ready real example, leaving a minor gap below anchor 5.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with state polling and a poll-again feedback loop, but the data-operation workflow (create/update students, proxy DELETE) has no validation or verification checkpoint before destructive/batch actions. Per the destructive/batch cap, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	No bundle files exist, so all content is inline in SKILL.md, but it is organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices). The large inline actions table is acceptable as a quick reference; structure is good with minor organization gaps, matching anchor 4.	4 / 5
	Total	14 / 20 Passed

Description

71%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 specific, low-conflict niche, though its trigger terms are limited to the platform name without synonyms. It is solid but could be sharpened with more concrete action verbs and natural trigger phrases.

Suggestions

Replace the single verb "Manage" with distinct concrete actions (e.g. "Create, list, update, and delete Documents, Templates, Users, and Groups") to lift specificity toward anchor 5.

Expand the "Use when" clause with natural trigger phrases a user would say, e.g. "Use when the user wants to create or retrieve Edusign students, courses, documents, or signatures".

Add common synonyms or related terms (signing, enrollments, transcripts) to broaden trigger-term coverage beyond just "Edusign data".

Dimension	Reasoning	Score
Specificity	"Manage Documents, Templates, Users, Groups" names the domain and four specific entity types, though all under the single generic verb "Manage". It lists several concrete targets but lacks distinct action verbs, sitting above anchor 3 and below the comprehensive coverage of anchor 5.	4 / 5
Completeness	It states both what ("Manage Documents, Templates, Users, Groups") and when ("Use when the user wants to interact with Edusign data"). Both are present, but the trigger clause is generic rather than listing concrete trigger phrases, matching anchor 4 rather than the explicit anchor 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Edusign data" surfaces the natural keyword "Edusign" but offers no synonyms or related phrasings (e.g. signing, documents, templates). This matches anchor 3: some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	"Edusign integration" and "interact with Edusign data" target a specific named platform, giving it a clear niche with minimal overlap risk against other skills, matching anchor 5.	5 / 5
	Total	16 / 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/edusign/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.