Name: d2l-brightspace
Rating: 62.4 (1 reviews)
Author: membranedev

d2l-brightspace

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

Quality

74%

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

Quality

Content

82%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 lean, highly actionable CLI integration guide with concrete commands and a well-sequenced connection workflow that includes real feedback loops. Its main weakness is the absence of validation/verification guidance around the destructive-capable proxy and action-run steps, and no use of reference files to offload detail.

Suggestions

Add a validation checkpoint before/after destructive proxy calls (e.g. 'For POST/PUT/DELETE, verify the returned state or re-fetch the resource before proceeding') to close the workflow gap.

Move the proxy flags table and clientAction state-handling detail into a short reference file linked from the body, improving progressive disclosure for a >50-line skill.

Trim the opening LMS background paragraph and the 'auth plumbing' prose to lift conciseness from good to lean.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands and a flags table that earn their tokens, with only minor trimmable prose such as the opening 'D2L Brightspace is a cloud-based learning management system...' paragraph and 'so you can focus on the integration logic rather than auth plumbing'; fits the 'efficient; minor instances of over-explanation' anchor rather than a 3 because the padding is incidental.	4 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run with --input JSON, request with a full proxy flags table) covering the common cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	There is a clear install→authenticate→connect→search→run sequence with explicit feedback loops in the connection flow (poll --wait until state leaves BUILDING, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action); fits anchor 4 because the run/proxy sections support destructive methods (DELETE/PUT) without an explicit verify step, a minor validation gap that keeps it below 5.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and no nested/multi-level references, and content is appropriately placed; fits anchor 4 rather than 5 because, at over 50 lines, none of the detail (proxy flags, clientAction handling) is offloaded to one-level-deep reference files, and rather than 3 because structure is clean with nothing clearly mis-placed.	4 / 5
	Total	17 / 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 its distinct niche (D2L Brightspace) and includes an explicit 'Use when' trigger, but the capability list is generic and the trigger terms lack the natural LMS-specific variations users would actually say. Tightening the actions and broadening trigger synonyms would lift completeness and trigger quality.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete operations like 'list courses, fetch grades, manage assignments and enrollments'.

Add natural trigger synonyms users say, e.g. 'Use when the user mentions Brightspace courses, assignments, grades, quizzes, or enrollments'.

Tie the 'when' clause to specific nouns (courses, gradebook, discussion forums) to make the trigger more concrete and reduce overlap ambiguity.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' — the domain is named and a few actions are listed, but the actions are generic rather than concrete, matching the anchor for naming a domain with 1-2 minimal/generic actions; not a 4 because no specific operations are enumerated.	3 / 5
Completeness	It states both what ('D2L Brightspace integration. Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with D2L Brightspace data'), matching the anchor for both present with the 'when' somewhat generic; not a 5 because the trigger is a single non-specific phrase rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	The natural keyword 'D2L Brightspace data' appears in the trigger ('Use when the user wants to interact with D2L Brightspace data'), but common variations users would say — courses, assignments, grades, quizzes — are missing, fitting the 'some relevant keywords but missing common variations' anchor; not a 4 due to thin synonym coverage.	3 / 5
Distinctiveness Conflict Risk	'D2L Brightspace' is a specific named product niche with a distinct brand trigger, giving minimal conflict risk with other skills; matches the 'clear niche with distinct triggers' anchor.	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/d2l-brightspace/SKILL.md
Commit: f484c82

Reviewed: ~16 hours 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.