CtrlK
BlogDocsLog inGet started
Tessl Logo

schoology

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

52

Quality

59%

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/schoology/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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's CLI workflow is concrete and executable with a clear connection sequence, but it is undermined by a massive inlined entity list containing many irrelevant items. Splitting that list into a reference file and pruning non-Schoology entries would improve both conciseness and structure.

Suggestions

Move the entity list into a separate references file and link to it from SKILL.md instead of inlining ~150 items.

Prune entries that are not Schoology API resources (e.g. security platforms, insurance policies) to cut padded tokens.

Add a validation/error-recovery step for action results, not just connection state, since running actions can be destructive or batch.

DimensionReasoningScore

Conciseness

The ~150-item entity list (including irrelevant entries like 'Cybersecurity Insurance Policy' and 'Threat Intelligence Platform') is heavily padded content that does not earn its tokens, while the CLI guidance is reasonably efficient, placing this noticeably below the midpoint.

2 / 5

Actionability

Concrete, executable CLI commands are provided throughout (install, login, connection ensure, action list/run, request flags table), with only minor gaps such as placeholder CONNECTION_ID values.

4 / 5

Workflow Clarity

The connection workflow is clearly sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling feedback, though validation of action results and error recovery beyond connection state has minor gaps.

4 / 5

Progressive Disclosure

Section headers organize the CLI guidance, but the large entity list is inlined monolithic content that clearly belongs in a separate reference file, and no bundle files exist to offload it.

3 / 5

Total

13

/

20

Passed

Description

62%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 adequate: it identifies a specific niche (Schoology), states both what and when, and uses a natural trigger term. Its main weakness is generic action verbs ('manage data, records, automate workflows') that lack concrete specificity.

Suggestions

Replace generic verbs with concrete Schoology actions, e.g. 'Create courses and assignments, manage enrollments, pull grades'.

Expand the trigger clause to mention natural user phrases like 'Schoology LMS', 'courses', 'assignments', or 'grades'.

DimensionReasoningScore

Specificity

Names the domain (Schoology) plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the anchor for domain plus 1-2 non-comprehensive actions.

3 / 5

Completeness

It states what ('Schoology integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Schoology data.'), though the 'when' could be more specific.

4 / 5

Trigger Term Quality

The natural keyword 'Schoology' appears in 'interact with Schoology data', but common variations or synonyms are missing, fitting the anchor for some relevant keywords without variations.

3 / 5

Distinctiveness Conflict Risk

Naming a specific product (Schoology) gives a clear niche with minimal conflict risk, though 'interact with Schoology data' is broad enough to risk minor overlap with generic data skills.

4 / 5

Total

14

/

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.