review-findings

Addresses and fixes findings from a QA code review. Reads the review report, fixes critical and warning issues, and prepares for re-verification. Delegates to the Forja (Dev) agent.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/agent-triforce/skills/review-findings/SKILL.md

Quality

Content

78%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 content is a concise, well-structured instruction-only workflow with concrete slash commands, a clear sequenced process, and explicit validation/verification checkpoints. The main gap is the absent error-recovery feedback loop when a finding cannot be addressed.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — numbered steps, slash-command examples, and a short Tips section with no padding — with only minor redundancy (the opening line restates the description), fitting "efficient; minor instances that could be trimmed" rather than the fully lean 5.	4 / 5
Actionability	Concrete slash commands (/review-findings, /review-findings docs/reviews/...) and named checklists (SIGN IN, Implementation Complete, Pre-Delivery/TIME OUT) give mostly executable guidance with minor gaps (how to invoke the Forja agent is unspecified), matching the 4 anchor.	4 / 5
Workflow Clarity	Eight steps are clearly sequenced with validation checkpoints (SIGN IN checklist, Implementation Complete/Pre-Delivery checklists, explicit verification of every Critical/Warning), but the error-recovery feedback loop when verification fails is only implicit, so it lands at 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist and the body is a short, self-contained, well-sectioned overview (~50 lines with clear headers); per the simple-skill exception this qualifies for the top anchor on organization alone.	5 / 5
	Total	17 / 20 Passed

Description

58%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 clearly conveys what the skill does with concrete, specific actions and a distinct niche, but it omits any explicit "Use when..." trigger guidance, which caps both completeness and trigger-term quality. Adding a trigger clause would lift the two weakest dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when a code review from Centinela (QA) returns findings that need fixing before re-verification."

Add natural user-facing synonyms (e.g. "code review", "review report", "fix review findings") so trigger terms match what a user would actually say.

Consider mentioning the input artifact (a review report path) to sharpen distinctiveness from generic fix/refactor skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Reads the review report", "fixes critical and warning issues", "prepares for re-verification", "Delegates to the Forja (Dev) agent" — with only minor coverage gaps, matching the "several specific actions" anchor rather than the comprehensive 5.	4 / 5
Completeness	The "what" is clearly stated but there is no "when"/"Use when..." clause; per the rubric a missing explicit trigger clause caps completeness at 3, which is the best-fitting anchor.	3 / 5
Trigger Term Quality	Relevant domain keywords ("QA code review", "findings", "critical and warning issues", "re-verification") are present but it lacks the natural "Use when..." phrasing and common synonyms a user would actually say, fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The niche is fairly distinct — fixing QA review findings and delegating to a named Forja agent — with only minor overlap risk against closely related review/fix skills, so it sits at 4 rather than the fully-distinct 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/agent-triforce/skills/review-findings/SKILL.md
Commit: ac92f1d

Reviewed: ~11 hours 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.