CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

address-feedback-with-replies

Fix the feedback in specific Slack threads or a named Slack scope and answer each reporter in-thread. Use when the user points at particular Slack feedback and says "address this feedback", "fix these and reply", or links threads. For a full sweep of the feedback channels use review-latest-feedback.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

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

An exemplary instruction-only skill body: dense and lean, unambiguous about what to do at each step, with real validation and error-recovery checkpoints, and clean delegation of shared detail to sibling skills. The batch operation (multiple Slack threads, PR merge) is fully covered by verification steps, so no cap applies.

DimensionReasoningScore

Conciseness

Every sentence carries an operational instruction ("Open every screenshot, file, video, transcript, and linked recording; the error text there is often the whole diagnosis") with no padding and no explanation of concepts Claude already knows.

5 / 5

Actionability

Highly concrete, executable instruction throughout: "add 👀 before investigating, one thread at a time", "Timebox one item to about 30 minutes", "run /ship through the merge, with every fixed thread's Slack link in the PR body's Reports section", plus a worked classification example ("Objectively broken (errors, dead clicks, lost or wrong data, regressions...): fix it").

5 / 5

Workflow Clarity

Six clearly sequenced stages (read → decide → clusters → fix/verify/ship → close the loop → recap) with explicit validation checkpoints and feedback loops: "verify as verifying-changes describes (a test that fails before and passes after)", "If the reaction fails, resolve that before going on", "confirm the reply landed under the right parent".

5 / 5

Progressive Disclosure

The body inlines only what is specific to working a given thread and delegates the shared contract to named sibling skills ("That skill owns the Slack contract... Read it first and follow it"), with a closing "Related skills" section; structure is clear with one-level-deep references and no bundle files are needed.

5 / 5

Total

20

/

20

Passed

Description

95%Weight 40%Scale 1-5

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 tight and operational: concrete actions with explicit quoted trigger phrases, a clear when-to-use clause, and an explicit boundary against the complementary sweep skill. Its only limitation is that the action list is brief, which is largely inherent to being a scoped variant of a broader skill.

DimensionReasoningScore

Specificity

Concrete actions are named and qualified — "Fix the feedback in specific Slack threads or a named Slack scope and answer each reporter in-thread" — which is noticeably more specific than the anchor-3 example, but only two core verbs are listed rather than the several actions of the anchor-5 example.

4 / 5

Completeness

Explicitly answers both what ("Fix the feedback in specific Slack threads... and answer each reporter in-thread") and when ("Use when the user points at particular Slack feedback and says 'address this feedback', 'fix these and reply', or links threads") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quotes the exact natural phrases a user would say — "address this feedback", "fix these and reply", "links threads" — alongside "Slack" and "feedback", giving comprehensive natural-term coverage for this domain.

5 / 5

Distinctiveness Conflict Risk

A clear niche (specific threads vs. the full sweep) with an explicit disambiguation boundary — "For a full sweep of the feedback channels use review-latest-feedback" — minimizing conflict risk with the sibling skill.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/skills/address-feedback-with-replies/SKILL.md

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.