CtrlK
BlogDocsLog inGet started
Tessl Logo

feedback

Send feedback to the Nexu team. Use when the user says /feedback followed by their message.

72

Quality

87%

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

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 content is actionable and clearly sequenced with a success/failure checkpoint, and it is well-structured for a simple single-purpose skill. Its main weakness is redundancy: the instruction to not manually gather conversation history or images is stated three times.

Suggestions

Consolidate the three repeated reminders about not manually providing conversation history/images into a single statement so each token earns its place.

Remove the duplicated guidance about placeholder replacement/escaping if it can be merged into one clearly marked note, reducing the Important section's length.

Verify submit-feedback.mjs is present in the skill bundle alongside SKILL.md so the referenced script path resolves at runtime.

DimensionReasoningScore

Conciseness

The body is mostly efficient but repeats the same point about not manually handling conversation history/images three times ("you do NOT need to copy-paste messages or scan for image URLs", "you do NOT need to provide them manually", "Do NOT manually build conversationContext or imageUrls"), which is padding.

2 / 3

Actionability

It provides a concrete, executable bash command with named flags and clearly marked placeholders, plus explicit escaping guidance, making it copy-paste ready.

3 / 3

Workflow Clarity

The four numbered steps are clearly sequenced, and step 4 branches on the script output ("{"ok":true}" vs failure) with distinct confirmation replies, providing an explicit validation/feedback checkpoint.

3 / 3

Progressive Disclosure

This is a simple, under-50-line single-task skill with well-organized sections (When triggered, Steps, Important) and a clearly signaled one-level reference to submit-feedback.mjs, which is appropriately split out from the instructions.

3 / 3

Total

11

/

12

Passed

Description

90%

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 concise and clearly answers both what the skill does and when to trigger it via an explicit /feedback command. It is third-person and free of fluff, with only minor room to broaden the action description beyond a single verb.

DimensionReasoningScore

Specificity

Names the domain (feedback) and a single concrete action ("Send feedback to the Nexu team"), but lists only one action rather than multiple specific concrete actions, matching the level-2 anchor.

2 / 3

Completeness

It explicitly states what it does ("Send feedback to the Nexu team") and when to use it ("Use when the user says /feedback..."), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

The phrase "Use when the user says /feedback followed by their message" gives the exact natural trigger a user would type; for a command-based skill this is the precise term users say, fitting the level-3 anchor.

3 / 3

Distinctiveness Conflict Risk

The /feedback slash command is a distinct, narrow trigger unlikely to overlap with other skills, giving it a clear niche with low conflict risk.

3 / 3

Total

11

/

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
nexu-io/nexu
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.