configure-factory-rules

Configure typed Mastra Factory rules and exact-leaf overrides in deployment code

Quality

72%

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 ./mastracode/factory/factory-skills/configure-factory-rules/SKILL.md

Quality

Content

87%

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 lean, highly actionable instruction set with strong organization and explicit validation steps; its main gap is the missing explicit error-recovery feedback loop in the verify workflow.

Suggestions

Add an explicit feedback loop in 'Verify the change', e.g. 'If tests, typecheck, or the Web build fail, fix the rule and re-run before proceeding.'

Provide a short ordering note or master sequence that connects the thematic sections into one end-to-end flow (Find configuration -> Apply override -> Bump version -> Verify).

Include a minimal code snippet showing the shape of an override (a typed FactoryRuleDecision return) to make the guidance copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and policy-dense with no over-explanation of concepts Claude already knows; every line states a concrete constraint or step and earns its place.	3 / 3
Actionability	It names specific symbols (new MastraFactory, defaultFactoryRules, FactoryRuleDecision, idempotencyKey), an exact file path (src/web/factory/rules/defaults.ts), the rules-tree shape, and concrete commands (tests, typecheck, Web build); per the scoring note, the absence of code in this instruction-only skill is not penalized because the guidance is actionable.	3 / 3
Workflow Clarity	Sections use numbered steps and 'Verify the change' lists explicit validation (tests, typecheck, build), but there is no explicit fix-and-revalidate feedback loop and no single end-to-end master sequence tying the thematic sections together.	2 / 3
Progressive Disclosure	The skill is self-contained with no bundle files and no nested references, organized into clearly delineated sections (Find, Preserve shape, Apply overrides, Version, Safety, Verify); for a single-purpose skill needing no external references, well-organized sections warrant the top score.	3 / 3
	Total	11 / 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 is specific to a distinct niche and names concrete actions, but it lacks an explicit 'Use when...' trigger clause and relies on somewhat technical jargon, capping completeness and trigger-term quality at the mid level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when changing Factory policy, adding rule overrides, or modifying work/review/tools/github handler behavior in deployment code.'

Broaden natural trigger terms with phrasings users would actually say ('add a Factory rule', 'override a handler', 'change deployment policy') alongside the jargon.

List one or two more concrete actions (e.g. the rule-tree categories) to lift specificity from domain-plus-some-actions to multiple specific actions.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('configure typed Mastra Factory rules' and 'exact-leaf overrides'), but the action list is narrow and not comprehensive, matching the level-2 anchor rather than the multi-action level-3 example.	2 / 3
Completeness	It clearly states what the skill does, but provides no 'Use when...' trigger or equivalent explicit when-guidance, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	'Factory rules' and 'overrides' are relevant in-domain terms, but 'exact-leaf overrides' is technical jargon and common phrasings a user might say ('add a Factory rule', 'override a handler') are missing.	2 / 3
Distinctiveness Conflict Risk	It targets a clear, narrow niche (typed Mastra Factory rules in deployment code) with distinct triggers, making it unlikely to fire for the wrong skill.	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/configure-factory-rules/SKILL.md
Commit: 3b78ed9

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