CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

address-feedback

Go through a feedback list (Notion, Google Doc, Linear, GitHub issue, pasted notes) and fix the real bugs, propose small UX changes, and flag the rest. Use when someone shares a feedback link or paste and says "address this feedback", "fix the bugs in this doc", or runs /address-feedback. For Slack feedback channels use review-latest-feedback; for specific Slack threads use address-feedback-with-replies.

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

96%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.

The body is a tightly written, highly actionable process skill: lean prose, concrete commands and criteria, an explicit verification gate before reporting, and a well-sequenced workflow. The only minor weakness is that all content (~105 lines) is inlined with no reference offload, leaving a small structural gap on progressive disclosure.

Suggestions

Move the item-classification criteria from section 2 (bug vs UX proposal vs unclear vs out of scope, plus the data/permissions/lifecycle checks) into a references/ file, keeping a short summary inline in SKILL.md.

If the repeat-detection search recipe grows (Sentry/Analytics/PR-title queries), extract it into a reference file so the main workflow stays under ~50 lines.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — e.g. "The error text in a screenshot is often the diagnosis" and "Reading the code is not verification" are dense heuristics with zero padding, and it never explains what Notion, Sentry, or Linear are. Every line carries instruction, matching the every-token-earns-its-place anchor.

5 / 5

Actionability

For an instruction-only skill the guidance is fully executable: a copy-paste report template, exact search scope ("Search three months back: the source, Sentry, Analytics errors, and merged PR titles, using the feature name, error text, and surface separately"), and concrete commands (Sentry org `builder-io`, `list-error-issues` / `get-error-issue`). Specific decision criteria cover the common classification cases.

5 / 5

Workflow Clarity

A clear 7-step numbered sequence (read/check repeats → sort → ask only when must → check error sources → choose fix altitude → fix and verify → report) with explicit validation checkpoints ("Don't say Fixed until it's verified", "a test that fails before and passes after") and a feedback loop for regressions ("Find why the first fix stopped holding and leave a test of the user's path that fails if it breaks again").

5 / 5

Progressive Disclosure

No bundle files exist, and the numbered sections plus clearly signaled cross-skill references (`verifying-changes`, `frontend-design`, `review-latest-feedback`) give good structure and easy navigation. However, at ~105 lines it exceeds the under-50-line simple-skill threshold and offloads nothing — the dense classification criteria in section 2 could optionally live in a reference file — so it fits the good-structure-with-minor-gaps anchor rather than a 5.

4 / 5

Total

19

/

20

Passed

Description

100%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 exemplary: concrete actions covering the full triage space, quoted natural trigger phrases, an explicit Use-when clause, and explicit de-confliction routing to sibling skills. It matches the strongest anchor on every dimension with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "fix the real bugs, propose small UX changes, and flag the rest" — and enumerates the source formats (Notion, Google Doc, Linear, GitHub issue, pasted notes). The three actions cover the complete outcome space of feedback triage, matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Explicitly answers both what ("fix the real bugs, propose small UX changes, and flag the rest") and when with concrete trigger phrases ("Use when someone shares a feedback link or paste and says 'address this feedback'..."). This is a direct match to the anchor requiring both what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes quoted natural user utterances — "address this feedback", "fix the bugs in this doc" — plus the /address-feedback command and synonyms across feedback/list/link/paste/notes/bugs. Coverage of natural phrasings and source-specific keywords is comprehensive, exceeding the good-coverage-with-a-few-missing anchor at 4.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear feedback-triage niche and explicitly routes overlapping cases to sibling skills ("For Slack feedback channels use review-latest-feedback; for specific Slack threads use address-feedback-with-replies"), which actively minimizes conflict risk. It is well above the minor-overlap anchor at 4.

5 / 5

Total

20

/

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