CtrlK
BlogDocsLog inGet started
Tessl Logo

diabatix-coldstream

Diabatix ColdStream integration. Manage data, records, and automate workflows. Use when the user wants to interact with Diabatix ColdStream 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/diabatix-coldstream/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 body is highly actionable with executable CLI commands and a clear connection-state workflow including validation via polling and error checks. It loses points only for minor verbosity and a couple of broken 'Step 2' cross-references.

Suggestions

Fix or remove the dangling 'skip to Step 2' references by labeling the downstream section as 'Step 2' or rewording to 'skip to Searching for actions'.

Move the proxy flag table and clientAction schema details into a referenced file to tighten SKILL.md and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands and minimal padding, though a few lines could be trimmed (e.g. 'This is the fastest way to get a connection' and 'so you can focus on the integration logic rather than auth plumbing').

4 / 5

Actionability

It provides copy-paste-ready, fully executable commands with explicit flags (--json, --wait, --timeout) and worked examples for install, auth, connection, action search/run, and proxy requests.

5 / 5

Workflow Clarity

The install→auth→connect→search→run sequence is clear with branching on READY/BUILDING/CLIENT_ACTION_REQUIRED and an error-field check, but the 'skip to Step 2' pointers reference a Step 2 that is not labeled, leaving a minor navigation gap.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized under clear headers with no nested references, but at ~140 lines some reference material (e.g. the proxy flag table and clientAction schema) could be split into a referenced file.

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 clearly identifies its niche via a proprietary product name and includes both a what and a when clause. It is weakest on action specificity and natural trigger-term variety, where the verbs stay generic.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete ColdStream actions, e.g. 'Run thermal simulations, retrieve design results, and manage project records'.

Expand the 'Use when' clause with concrete trigger phrases users would say, e.g. 'Use when the user wants to run a ColdStream thermal simulation, check a heat-sink design result, or query ColdStream project data'.

DimensionReasoningScore

Specificity

Names the Diabatix ColdStream domain and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concretely specific to the thermal-design platform, so it does not reach the 'several specific actions' bar of 4.

3 / 5

Completeness

It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Diabatix ColdStream data'), though the 'when' clause could be more specific with concrete trigger phrases.

4 / 5

Trigger Term Quality

It repeats 'Diabatix ColdStream' as the natural keyword, but offers few synonyms or varied phrasings a user would naturally say (no 'thermal simulation', 'heat sink', or file extensions), leaving common variations missing.

3 / 5

Distinctiveness Conflict Risk

The proprietary product name 'Diabatix ColdStream' creates a clear niche with distinct triggers and minimal risk of colliding with other skills.

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.