CtrlK
BlogDocsLog inGet started
Tessl Logo

interactive-teaching-materials

Creates interactive HTML teaching materials with clickable state diagrams. Use when the user asks to produce an explorable tutorial artifact, not to answer a question.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

83%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 exceptionally lean and actionable, with complete data schemas and real template bundles for both diagram types. Its one gap is the workflow: generating artifacts from templates has no explicit validation step despite the skill's own anti-patterns about empty descriptions and overloaded diagrams.

Suggestions

Add an explicit validation checkpoint to the workflow, e.g. 'Open the file in a browser and confirm every node/edge opens a non-empty detail panel; reject any element with empty description or details'.

Tie the validation step to the anti-patterns (no empty descriptions, no 40+ element overload) so the quality bar is enforced rather than merely stated.

DimensionReasoningScore

Conciseness

The body is lean: principles, anti-patterns, a data schema with inline comments, and constraints — every section earns its place and assumes Claude's competence without explaining basic HTML/SVG concepts.

5 / 5

Actionability

It provides complete executable data schemas for both sequence and flowchart diagrams with required/optional fields, node shapes, and a concrete workflow pointing to working templates that embed a real DATA section to replace.

5 / 5

Workflow Clarity

The 4-step workflow is sequenced, but it involves generating an HTML artifact from a template with no validation/verification checkpoint (e.g. open in browser, confirm all elements have details, check for empty descriptions), which the anti-patterns imply but the workflow does not enforce.

3 / 5

Progressive Disclosure

Structure is good: SKILL.md is an overview with schemas and principles, and full working examples are correctly offloaded to assets/flowchart.html and assets/sequence.html (verified to exist with the referenced DATA markers); references are clear but bulk template logic lives inline in the bundle rather than being separately navigable.

4 / 5

Total

17

/

20

Passed

Description

80%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 concise, third-person, and clearly answers both what the skill does and when to use it, with a strong distinctiveness signal via the Mermaid contrast. Its main limitation is modest coverage of trigger synonyms and concrete action variations.

Suggestions

Add a couple of natural trigger synonyms (e.g. 'interactive diagram', 'explorable flowchart', 'clickable tutorial') to broaden when-clause coverage.

Expand the action list slightly (e.g. 'build clickable sequence and flowchart diagrams with rich per-element detail panels') to increase specificity beyond a single artifact type.

DimensionReasoningScore

Specificity

It names the concrete artifact ('interactive HTML teaching materials with clickable state diagrams') and the core action, but lists only one primary action rather than a comprehensive set of operations, leaving minor coverage gaps.

4 / 5

Completeness

It answers both 'what' (creates interactive HTML teaching materials with clickable state diagrams) and 'when' ('Use when the user asks to produce an explorable tutorial artifact, not to answer a question'); the 'when' is explicit but somewhat narrow in scope.

4 / 5

Trigger Term Quality

'interactive HTML teaching materials', 'clickable state diagrams', and 'explorable tutorial artifact' are natural phrases a user would say, though synonyms like 'interactive diagram' or file-type triggers are not exhaustively covered.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly distinct — explorable tutorial artifacts with clickable state diagrams — and the explicit contrast with answering questions and with Mermaid one-word labels minimizes overlap with other diagram skills.

5 / 5

Total

17

/

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
korchasa/flowai-plugins
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.