CtrlK
BlogDocsLog inGet started
Tessl Logo

ray-skill

Use when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in the Ray desktop application.

71

Quality

88%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable and well-structured reference content with concrete, copy-paste-ready examples and a clear single action. The main weaknesses are repetitive origin objects and a redundant summary table that hurt conciseness, plus a long monolithic layout that could benefit from splitting detail into a reference file.

Suggestions

Define the origin object once and abbreviate it in subsequent payload examples (e.g., "origin": { ... }) to remove repeated boilerplate and tighten the body.

Remove or fold the trailing "Payload Type Reference" table into the per-type sections to eliminate redundant restatement of the same fields.

Move the detailed payload-type catalog into a separate reference file (e.g., references/payload-types.md) and keep SKILL.md as a concise overview with a one-level-deep link, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient tables and JSON, but it repeats the full origin object (file, line_number, hostname) in every payload example and closes with a "Payload Type Reference" table that restates the per-type sections above — content that could be tightened.

2 / 3

Actionability

Connection details, a complete curl example, concrete JSON payloads for every type, and an availability-check endpoint make the guidance fully executable and copy-paste ready.

3 / 3

Workflow Clarity

The core action (POST payloads to Ray) is unambiguous for this single-purpose skill, and an availability pre-check is documented; since sending debug data is neither destructive nor batch, no validation feedback loop is required to reach the top anchor.

3 / 3

Progressive Disclosure

Sections and tables are well organized, but the 343-line file is monolithic with detailed payload-type reference material that could be split into a separate reference file, and no bundle references are used despite the length.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete capabilities, opens with explicit "Use when …" triggers phrased as natural user utterances, and is tied to a distinct named application. It cleanly addresses what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," plus "visualize data, debug output, or show diagrams" — matching the anchor for several specific concrete actions.

3 / 3

Completeness

It explicitly answers both what (visualize data, debug output, show diagrams in the Ray desktop application) and when ("Use when user says …"), satisfying the top anchor for both what AND when.

3 / 3

Trigger Term Quality

The description is built from natural phrases a user would actually say ("send to Ray," "debug in Ray," "log to Ray"), giving good coverage of natural trigger terms.

3 / 3

Distinctiveness Conflict Risk

"Ray" is a specific named desktop application with distinct trigger phrases, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
freekmurze/dotfiles
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.