Name: degreed
Rating: 52.8 (1 reviews)
Author: membranedev

degreed

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

Quality

59%

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/degreed/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 Membrane CLI guidance with a well-sequenced connection workflow and a useful state-feedback loop, but it carries some unnecessary background prose, lacks post-action validation, and its 'Popular actions' section under-delivers by not naming real Degreed actions. Tightening the intro and adding verification steps would raise it further.

Suggestions

Remove or trim the opening paragraph explaining what Degreed is and the 'focus on integration logic rather than auth plumbing' commentary to respect Claude's existing knowledge.

Add a validation/verify step after running actions or proxy requests (e.g. inspect the `output` field for errors, re-check state on failure) to satisfy the destructive-operation feedback-loop expectation.

Replace the 'Popular actions' section's repeated discovery command with 2-3 named Degreed actions or example intents so the most common use cases are concrete.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-focused, but the opening paragraph explaining what Degreed is and padding like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation Claude does not need, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands (install, login, connection ensure, action list/run, request) plus a flags table, but 'Popular actions' only repeats the discovery command instead of listing actual Degreed actions, leaving a minor gap below the fully-covered level-5 anchor.	4 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence is clear and the connection step has a state-polling feedback loop, but there is no validation or verify step after running actions or proxy requests that can mutate Degreed data, so the destructive-operation cap of 3 applies rather than the level-4 checkpoint anchor.	3 / 5
Progressive Disclosure	As a single-file skill with no bundle, it is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with easy navigation, fitting the 'good structure; most content appropriately placed; minor organization gaps' anchor; the sparse 'Degreed Overview' bullet list is the main minor gap.	4 / 5
	Total	14 / 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 correctly includes an explicit 'Use when' clause and ties the skill to a distinct named product, but its action list is generic and its trigger phrasing lacks concrete Degreed-specific terms. It is functional but could be sharpened with specific capabilities and natural user phrases.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Degreed operations, e.g. 'search learning content, manage paths and skills, pull completion records'.

Expand the trigger with natural user phrases such as 'Use when the user wants to search Degreed courses, enroll users in paths, or pull Degreed completion reports.'

Add 1-2 synonyms or specific Degreed entities (paths, skills, content) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the Degreed domain but the actions ('Manage data, records, and automate workflows') are generic verbs, not concrete Degreed-specific operations, matching the 'names the domain but actions are minimal or generic' anchor rather than the concrete-action anchor above.	2 / 5
Completeness	It states both what ('Degreed integration. Manage data, records, and automate workflows.') and an explicit when ('Use when the user wants to interact with Degreed data.'), but the trigger is generic rather than concrete, fitting the 'both what and when; when could be more specific' anchor below the level-5 concrete-trigger anchor.	4 / 5
Trigger Term Quality	'Degreed' and 'interact with Degreed data' provide a relevant keyword and trigger, but common natural variations a user might say (search courses, pull reports, enroll in paths) are missing, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product 'Degreed' gives a clear niche with minimal conflict risk, but the generic 'interact with Degreed data' trigger and broad action list leave minor overlap risk, fitting the 'mostly distinct; minor overlap risk' anchor rather than the level-5 distinct-triggers anchor.	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/degreed/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.