CtrlK
BlogDocsLog inGet started
Tessl Logo

script-read

Read a `.cs` script file and return its content as a string. Supports a 1-based `lineFrom`/`lineTo` slice for partial reads. Pair with 'script-update-or-create' to write back.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./Unity-MCP-Plugin/.claude/skills/script-read/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is actionable and well-structured for a simple single-tool skill, with executable commands and complete schemas. The one notable issue is redundant repetition of the three parameters across three sections, which slightly hurts token efficiency.

Suggestions

Eliminate the duplicated parameter list: keep either the 'Inputs' bullet list or the 'Input' table plus JSON schema, not all three, to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no concept-explaining filler, but the three parameters (filePath/lineFrom/lineTo) are repeated across the 'Inputs' list, the 'Input' table, and the Input JSON Schema, which is padding that could be consolidated.

2 / 3

Actionability

It provides a fully executable CLI command, an input-file/stdin variant, a concrete troubleshooting install command, and complete input/output JSON schemas with a sample path, all copy-paste ready.

3 / 3

Workflow Clarity

This is a simple single-action skill whose action is unambiguous ('Reads the file with File.ReadAllLines and slices [lineFrom..lineTo]'), and it involves no destructive or batch operation that would require validation checkpoints, so the simple-skill guidance allows a 3.

3 / 3

Progressive Disclosure

The single self-contained file is organized into clear, well-labeled sections (Inputs, Behavior, How to Call, Troubleshooting, Input, Output) with no nested references and no content that needs splitting out, satisfying appropriate structure for a one-tool skill.

3 / 3

Total

11

/

12

Passed

Description

67%

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 specific and distinctive, clearly conveying what the skill does for `.cs` files. Its main weakness is the absence of explicit 'when to use' trigger guidance, capping completeness, and trigger terms that are somewhat technical rather than natural.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrasing, e.g. 'Use when you need to read, view, or inspect a .cs script file, or take a partial line slice of its contents.'

Broaden trigger terms with common natural wording ('view', 'open', 'get file content') alongside the technical 'lineFrom/lineTo' parameters.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Read a `.cs` script file and return its content as a string' and 'Supports a 1-based `lineFrom`/`lineTo` slice for partial reads' — which matches the anchor for listing several specific concrete actions rather than merely naming a domain.

3 / 3

Completeness

It clearly answers 'what' (read and slice) but offers only an implied 'when' via the pairing hint rather than an explicit 'Use when...' trigger clause, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

It includes relevant terms (`.cs`, 'script file', 'read', 'lineFrom/lineTo') but these skew technical and omit common natural phrasing a user might say (e.g., 'view', 'open', 'get file content'), matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The scope is tightly bound to `.cs` script reads with a named sibling tool ('script-update-or-create'), giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
IvanMurzak/Unity-MCP
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.