Name: instruqt
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

instruqt

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/instruqt/SKILL.md

Quality

Content

67%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 well-organized, command-rich integration guide with a genuine polling feedback loop for connection setup, but it carries some platform background padding, relies on placeholders rather than a concrete worked example, and has broken step numbering.

Suggestions

Trim the background paragraph and the 'auth plumbing' / 'fastest way to get a connection' filler so every line is operational.

Fix the step numbering: label sections Step 1/Step 2 consistently or remove the dangling 'skip to Step 2' and '1b' references.

Add one fully concrete end-to-end example with real-looking values (a specific action id and connection id) and a post-run validation/check step for action results.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-focused content, but the opening platform background ('Instruqt is a virtual IT lab platform...'), the 'so you can focus on the integration logic rather than auth plumbing' line, and 'This is the fastest way to get a connection' add unnecessary explanation Claude does not need, fitting anchor 3 'Mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Concrete executable commands are provided throughout (install, login, connection ensure, action list/run, request) with a flags table, but they rely on placeholders (CONNECTION_ID, <actionId>, <id>) with no fully concrete end-to-end example and a minor membrane-vs-npx invocation inconsistency, matching anchor 4 'Mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The connect-then-poll sequence has an explicit feedback loop (BUILDING -> CLIENT_ACTION_REQUIRED -> READY with re-polling), but the step numbering is broken ('skip to Step 2' with no Step 2 heading, '1b' with no '1a') and post-run validation is absent, fitting anchor 4 'Clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inline, but the single SKILL.md is well-sectioned (Overview, Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with clear headers making it navigable, matching anchor 4 'Good structure; most content is appropriately placed; minor organization gaps'.	4 / 5
	Total	15 / 20 Passed

Description

61%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 pairs a what-and-when structure and leverages a distinctive proper-noun trigger, but its action verbs are generic and it omits Instruqt-specific entity terms that users would naturally say.

Suggestions

Replace generic verbs with Instruqt-specific operations, e.g. 'Create tracks and challenges, manage environments and users, and automate lab workflows'.

Expand the trigger phrase to include natural synonyms users say, e.g. 'Use when the user wants to work with Instruqt tracks, challenges, labs, or training data'.

Name the concrete objects (tracks, challenges, learning paths, environments) so the skill is distinguishable and triggerable by entity name.

Dimension	Reasoning	Score
Specificity	Phrases 'Manage data, records, and automate workflows' name the domain but the actions are generic/abstract rather than concrete Instruqt operations (e.g. tracks, challenges, environments are never mentioned), matching anchor 2 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It states both what ('Instruqt integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Instruqt data'), but the when is a single generic trigger and could be more specific, matching anchor 4 'Has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	The natural keyword 'Instruqt' (and 'Instruqt data') is present, but common user variations like 'tracks', 'challenges', 'labs', or 'training' are missing, fitting anchor 3 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Instruqt' is a unique proper-noun platform name giving a clear niche with minimal conflict risk against other skills, matching anchor 5 'Clear niche with distinct triggers; minimal conflict risk'.	5 / 5
	Total	14 / 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/instruqt/SKILL.md
Commit: f484c82

Reviewed: 5 days 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.