CtrlK
BlogDocsLog inGet started
Tessl Logo

act-on-feedback

Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./src/vs/sessions/skills/act-on-feedback/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The skill body is concise and well-organized for a simple single-purpose task, but its instructions are mildly abstract and its verification step lacks an explicit feedback loop for handling failures.

Suggestions

Add concrete detail to the action steps, such as where attached feedback comments are found and how to map each comment to the specific change it targets.

Turn the 'Verify' step into an explicit validation loop: if a change conflicts with the codebase, describe fixing it and re-verifying before proceeding.

Briefly specify the expected output or confirmation once all feedback is addressed so completion is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean with no concept-padding Claude already knows; every line is a direct instruction and each token earns its place, matching the 'lean and efficient' level 3 anchor.

3 / 3

Actionability

Steps like 'Make the requested changes' and 'Verify your changes are consistent with the rest of the codebase' give concrete direction but remain somewhat abstract without specifics on how to locate or apply each comment, matching the 'some concrete guidance but incomplete' anchor.

2 / 3

Workflow Clarity

The five numbered steps provide a clear sequence, but the lone 'Verify' step is an implicit checkpoint with no error-recovery or re-verification loop, matching the 'steps listed but validation gaps' anchor.

2 / 3

Progressive Disclosure

This is a simple under-50-line single-task skill with a clean single heading and no need for external references, which the rubric allows to score 3 for well-organized content.

3 / 3

Total

10

/

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 cleanly answers both what the skill does and when to trigger it with an explicit 'Use when' clause, but its capability list is thin and 'feedback' is a somewhat generic trigger term that risks overlap with adjacent skills.

Suggestions

Enumerate the concrete actions the skill performs (e.g., 'review, interpret, and apply feedback comments to your changes') to lift specificity from a single action to multiple.

Broaden trigger terms to natural variations users would say, such as 'feedback comments', 'review notes', or 'revision requests', to improve trigger coverage and reduce conflict with general review skills.

DimensionReasoningScore

Specificity

The description names the feedback domain and the act-on-feedback action but lists only a single concrete action rather than multiple specific ones, matching the 'names domain and some actions' anchor and falling short of the multi-action level 3.

2 / 3

Completeness

It explicitly states both what it does ('Act on user feedback attached to the current session') and when to use it ('Use when the user submits feedback... via the Submit Feedback button'), satisfying the explicit what-and-when level 3 anchor.

3 / 3

Trigger Term Quality

'feedback' and 'Submit Feedback button' are natural user terms, but coverage is thin with missing common variations such as 'comments' or 'review changes', matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The 'Submit Feedback button' trigger is somewhat distinctive, but 'feedback' is generic and could overlap with general code-review skills, matching the 'somewhat specific but could still overlap' anchor rather than the clear-niche level 3.

2 / 3

Total

9

/

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
posit-dev/positron
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.