factory-review

Review a pull request for a Factory work item — history and context first, then verdict — and mark the review complete

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./mastracode/factory/factory-skills/factory-review/SKILL.md

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 content is lean, highly actionable, and well-sequenced with explicit validation checkpoints and a retry feedback loop for the governed transition, with no padding or misplaced detail.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive, assumes Claude's competence (no explanations of git/gh/PR concepts), and every section earns its place; there is no concept-padding or verbosity.	3 / 3
Actionability	It provides fully executable guidance: concrete `gh pr view/diff/check` commands with exact --json/--jq flags, `git log --oneline -20 -- <file>` and `git blame`, plus the `factory_transition_work_item` call with named parameters and a 1000-char rationale constraint.	3 / 3
Workflow Clarity	Phases 1–5 are clearly sequenced, Phase 2 provides an explicit quality gate, and Phase 5 includes a concrete feedback loop (transition rejected → read reason → address → re-check revision → retry once), matching the anchor for clear sequence with validation and error-recovery loops.	3 / 3
Progressive Disclosure	The skill is a single cohesive multi-phase workflow with no external references needed and no inline content that should be split out; it is well-organized into Phases and Behavior Rules, and no bundle files exist to verify against.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 identifies a distinct niche and states what the skill does, but lacks an explicit 'Use when' trigger clause and omits common keyword variations like 'PR', leaving several dimensions at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reviewing a pull request for a Factory work item, or when asked to review a PR before marking the work item done.'

Include natural keyword variations users would say, such as 'PR', 'code review', and 'work item review', alongside 'pull request'.

List the concrete review actions more explicitly (e.g. 'judge correctness, tests, scope, and pattern consistency') to lift specificity toward 3.

Dimension	Reasoning	Score
Specificity	Names the domain ('pull request', 'Factory work item') and a couple of actions ('verdict', 'mark the review complete'), but the actions are process-oriented rather than a comprehensive list of discrete concrete capabilities, so it falls short of the multi-action anchor at 3.	2 / 3
Completeness	It clearly states what the skill does, but the 'when' is only implied by 'for a Factory work item' with no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant natural terms ('pull request', 'review') but 'Factory work item' is domain jargon and common variations like 'PR' are missing, so it matches 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The Factory-work-item / pull-request-review niche is specific and distinct, making it unlikely to trigger for the wrong skill; this matches the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: mastra-ai/mastra
Path: mastracode/factory/factory-skills/factory-review/SKILL.md
Commit: 3b78ed9

Reviewed: 1 day 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.