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

Blog Docs Log in Get started

edlink

Edlink integration. Manage data, records, and automate workflows. Use when the user wants to interact with Edlink 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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 executable CLI commands and a clear connection-to-execution workflow including state-based feedback loops. It loses points mainly on conciseness (some inferable padding and a vague data-model section) and minor workflow/organization inconsistencies.

Suggestions

Trim inferable prose such as 'This eliminates the need for individual integrations...' and 'so you can focus on the integration logic rather than auth plumbing' to save tokens.

Fix the inconsistent step numbering — 'If state is READY, skip to Step 2' references a step that isn't labeled 'Step 2'; rename '1b' to a clean sequential step.

Replace the vague data-model note 'Use action names and parameters as needed' with a concrete pointer (e.g. 'Use `membrane action list` to discover the parameters for each entity') or remove it.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but includes unnecessary filler ('This eliminates the need for individual integrations', 'so you can focus on the integration logic rather than auth plumbing') that explains things Claude can infer, and the data-model overview is vague ('Use action names and parameters as needed').	3 / 5
Actionability	Every section gives copy-paste-ready CLI commands with flags (install, login, connection ensure/get, action list/run, request proxy) plus a flag table; the common cases are fully covered with executable examples.	5 / 5
Workflow Clarity	There is a clear connect -> wait-for-ready -> search-actions -> run sequence with state-based branching (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and an explicit re-poll feedback loop, but the numbered step labeling is inconsistent ('Step 2', '1b') and some entry points are ambiguous.	4 / 5
Progressive Disclosure	Content is well organized into clear sections with no bundle files referenced (none exist); the SKILL.md stands alone as a single-level overview. Minor gaps: the data-model hierarchy is inlined with little explanation and 'Popular actions' repeats the discovery command without pointing to detail.	4 / 5
	Total	16 / 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 has a clear trigger clause and a distinct product niche, but its capability verbs are generic ('Manage data, records, and automate workflows') rather than concrete actions. Tightening the action list with specific Edlink operations would lift specificity and trigger coverage.

Suggestions

Replace generic verbs with concrete Edlink actions, e.g. 'List students and courses, retrieve assignments and submissions, and automate Edlink workflows.'

Expand the trigger clause with natural user phrases, e.g. 'Use when the user wants to query student, course, or assignment data from Edlink.'

Add entity nouns users actually mention (students, teachers, courses, assignments, submissions) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain (Edlink) and lists generic verbs ('Manage data, records, and automate workflows') but no concrete actions comparable to 'extract', 'fill forms', or 'merge'; actions are minimal and generic.	2 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Edlink data'), but the 'when' is somewhat generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Edlink data' supplies the natural trigger term 'Edlink data', but coverage is thin — no synonyms, no file types or entity names (students, courses, submissions) users would naturally say.	3 / 5
Distinctiveness Conflict Risk	The 'Edlink' name gives it a clear niche distinct from most skills; minor overlap risk with other data-integration skills, but the specific product name keeps conflict low.	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/edlink/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.