factory-triage

Triage a Factory work item's issue — trace history, understand architecture, diagnose root cause, then advance the stage

Quality

60%

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-triage/SKILL.md

Quality

Content

67%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 well-structured, actionable triage workflow with concrete commands and a clear phase sequence including a governed-transition feedback loop, though it is somewhat long with a few repeated directives and relies entirely on a single inlined file.

Suggestions

Tighten repeated directives (decision rule, label-mutation guidance appears in multiple phases) to reduce token cost and improve conciseness.

Provide concrete Linear-equivalent commands or examples alongside the GitHub gh commands so the Linear branch is as actionable as the GitHub branch.

Consider extracting the label-mutation rules and severity/effort/impact guides into a reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence, but at ~180 lines it includes some padded guidance and repeated directives (e.g., decision-rule restated, label mutation rules re-explained) that could be tightened.	3 / 5
Actionability	Provides concrete, executable commands (gh CLI calls, jq filters, bash snippets for label reconciliation and comment lookup) covering the common cases, with only minor gaps such as the Linear branch lacking equivalent concrete commands.	4 / 5
Workflow Clarity	A clear five-phase sequence with explicit checkpoints and an error-recovery feedback loop (handle transition rejection, re-check revision, retry once), plus validation of marker-comment ownership; minor gaps in explicit per-phase validation.	4 / 5
Progressive Disclosure	Good single-file structure with well-organized sections (phases, output contract, behavior rules) and clear in-place templates; no bundle files exist, so all content lives in SKILL.md, but it is appropriately sectioned with minor inlining of content that could conceptually be split.	4 / 5
	Total	15 / 20 Passed

Description

53%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 communicates what the skill does within the Factory domain using concrete process verbs, but it lacks an explicit 'Use when...' trigger clause and leans on internal jargon rather than natural user phrases.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when triaging a Factory work item's issue or advancing its triage stage').

Include a few natural user-facing trigger phrases or synonyms beyond Factory-internal terminology to improve trigger term quality.

Consider naming additional concrete actions (e.g., 'post a handoff comment', 'reconcile triage labels', 'request stage transition') for fuller capability coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Factory work item issue triage) and 1-2 concrete actions ('trace history', 'diagnose root cause', 'advance the stage'), but the actions are somewhat abstract process verbs rather than a comprehensive list of specific operations.	3 / 5
Completeness	There is a clear 'what' (triage the issue: trace history, understand architecture, diagnose root cause, advance stage) but no explicit 'when'/'Use when...' trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Contains relevant keywords ('triage', 'work item', 'issue', 'root cause', 'stage') but uses internal Factory-domain jargon rather than natural user-facing trigger phrases; no common synonyms or variations are present.	3 / 5
Distinctiveness Conflict Risk	The skill targets a very specific Factory-work-item triage niche with distinct triggers (governed stage transition, Factory session), giving it a clear niche with only minor overlap risk against generic code-investigation skills.	4 / 5
	Total	13 / 20 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-triage/SKILL.md
Commit: d6ce34a

Reviewed: about 18 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.