CtrlK
BlogDocsLog inGet started
Tessl Logo

classlink

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

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/classlink/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is a strong, actionable CLI integration guide with executable commands and a well-sequenced connection workflow that includes validation checkpoints. Minor conciseness and step-numbering polish would bring it to the top level.

Suggestions

De-duplicate the action-discovery command (it appears in both "Searching for actions" and "Popular actions") to tighten token use.

Fix the workflow numbering so "Step 2" is an actual labeled heading and "1b" is folded into a coherent numbered sequence.

Expand the bare ClassLink Overview bullet list (User/App/Roster/OneRoster API) into a sentence or remove it, since a content-free outline adds little.

DimensionReasoningScore

Conciseness

The body is mostly lean with executable commands and brief framing, but includes minor redundancy (the action-list search command appears twice) and a light product backgrounder that could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready, fully executable commands for install, login, connection, action search/run with JSON input, and a proxy flag table covering the common cases.

5 / 5

Workflow Clarity

The connection flow has a clear sequence with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-complete-poll feedback loop, but loose numbering ("1b", an unlabeled "Step 2") introduces minor gaps.

4 / 5

Progressive Disclosure

With no bundle files present, the self-contained ~140-line guide is well-organized into clear sections; the bare ClassLink Overview bullet list and absence of any reference split are minor organization gaps.

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 is third-person and cleanly states a distinct ClassLink niche with an explicit use-trigger, but its capability list is generic ("manage data, automate workflows") rather than concrete. Tightening the "what" with specific capabilities would lift specificity and completeness.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete ClassLink capabilities, e.g. roster/user/app lookups, OneRoster API queries, or SSO actions.

Add natural trigger synonyms in the use clause, such as "rosters", "OneRoster", or "student/teacher accounts", so it matches varied user phrasings.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the ClassLink domain with a couple of broad actions, but the actions are generic rather than concrete capabilities, fitting the anchor for naming a domain with 1-2 non-comprehensive actions.

3 / 5

Completeness

It states both a "what" (manage data, records, automate workflows) and an explicit "when" (use when interacting with ClassLink data), though the "what" lacks concrete granularity, keeping it just below a 5.

4 / 5

Trigger Term Quality

"Use when the user wants to interact with ClassLink data" supplies the natural term "ClassLink data", but lacks common variations or synonyms beyond the single product name.

3 / 5

Distinctiveness Conflict Risk

"ClassLink integration" names a specific product niche with a distinct trigger, making it unlikely to be selected for the wrong skill.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.