CtrlK
BlogDocsLog inGet started
Tessl Logo

neural-link

Expert tactical knowledge on sequencing Neural Link MCP tools to inspect, debug, and manipulate live Neo.mjs applications. Triggers: Use this skill if the user asks you to interact with the browser, inspect the UI natively, patch live code, or use the Neural Link.

80

Quality

100%

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

100%Weight 40%Scale 1-3

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

The SKILL.md body is a model progressive-disclosure pointer: lean, concrete, and unambiguous about the mandatory first step, with all detailed substance correctly offloaded to a single verified reference file. It scores well across conciseness, actionability, workflow clarity, and disclosure.

DimensionReasoningScore

Conciseness

The body is a single lean sentence with no padding or explanation of concepts Claude already knows; every token earns its place, matching the lean-and-efficient anchor.

3 / 3

Actionability

It names the exact tool (`view_file`), the exact reference path, and a strict ordering precondition, giving a fully concrete and executable first action; the code-vs-instruction note protects this pointer skill from an inline-code penalty.

3 / 3

Workflow Clarity

It establishes an unambiguous single-step workflow with an explicit gating checkpoint (read the handbook before invoking any native MCP tools), and the referenced handbook contains the detailed verification-backed chains.

3 / 3

Progressive Disclosure

The body is a clear overview pointing to one well-signaled, one-level-deep reference (verified to exist at references/operational-handbook.md) with no deeper nesting, matching the clear-overview-with-one-level-deep-references anchor.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, third-person, and clearly separates capabilities from explicit trigger guidance. It names a distinct niche with concrete actions and natural trigger terms, scoring well across all dimensions.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "inspect, debug, and manipulate live Neo.mjs applications" plus "interact with the browser, inspect the UI natively, patch live code" — matching the "lists multiple specific concrete actions" anchor.

3 / 3

Completeness

Clearly answers both what ("Expert tactical knowledge on sequencing Neural Link MCP tools…") and when (explicit "Triggers: Use this skill if…" clause), satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

An explicit "Triggers:" clause gives a broad spread of natural user phrasings (interact with the browser, inspect the UI natively, patch live code, use the Neural Link), covering what a user debugging a live app would actually say.

3 / 3

Distinctiveness Conflict Risk

The Neural Link + Neo.mjs + live-patching niche is specific with distinct triggers naming a particular toolset, making conflict with other skills unlikely.

3 / 3

Total

12

/

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
neomjs/neo
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.