address-feedback

Triage feedback docs or pasted feedback into bugs to fix, UX suggestions to propose, unclear questions, and skipped noise; verify bugs, check Sentry when relevant, and keep UI changes minimal.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%

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 tight, well-structured instruction skill: concrete categorization, sequenced steps with verification checkpoints, a copy-ready report template, and a clear avoid-list. It respects Claude's competence and is fully actionable without verbosity.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no explanation of concepts Claude already knows; every section (Prerequisites, Steps, Report Format, Avoid) earns its place and assumes competence.	3 / 3
Actionability	Provides concrete, specific guidance: a source-reader table, a four-category taxonomy with definitions, specific Sentry search strategy, named UI patterns (DropdownMenu, Popover, Sheet), and a copy-ready report template — fully actionable for an instruction-only skill.	3 / 3
Workflow Clarity	A clearly sequenced 6-step process with explicit validation checkpoints ('Verify before fixing', 'Run the smallest relevant test or typecheck', 'inspect the actual screen'), including feedback loops for error recovery.	3 / 3
Progressive Disclosure	A single-purpose skill under ~100 lines with no external bundle files, organized into well-signaled sections (Prerequisites, Steps, Report Format, Avoid, Related Skills); per the simple-skills note this earns a 3 with just well-organized sections.	3 / 3
	Total	12 / 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 is specific and distinctive, clearly conveying a feedback-triage niche with concrete actions. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and leaves trigger-term phrasing slightly less natural.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user shares a feedback document, issue thread, or pasted notes and asks you to act on them.'

Soften jargon like 'triage' and 'skipped noise' or pair them with natural terms users would actually say (e.g. 'feedback', 'issues', 'ignore low-signal items').

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'bugs to fix, UX suggestions to propose, unclear questions, and skipped noise; verify bugs, check Sentry ... keep UI changes minimal', matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly states what the skill does but the 'when to use it' trigger is only implied via 'Triage feedback docs or pasted feedback'; there is no explicit 'Use when...' clause, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Has relevant keywords ('feedback docs', 'pasted feedback', 'bugs', 'Sentry') but terms like 'triage' and 'skipped noise' are somewhat jargon-y and miss common natural variations, so it stops short of the full coverage anchor.	2 / 3
Distinctiveness Conflict Risk	A clear niche (addressing user feedback) with distinct triggers ('feedback docs', 'pasted feedback', 'check Sentry') that is unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: c1ee18b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.