CtrlK
BlogDocsLog inGet started
Tessl Logo

configure-factory-rules

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

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tight, well-structured operational guide with strong workflow sequencing and validation checkpoints, assuming Claude's intelligence throughout. The only gap is the absence of copy-paste code examples, which keeps actionability at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept explanations, no padding, every line is actionable guidance, fitting the 5 anchor.

5 / 5

Actionability

Concrete file paths, typed contracts (FactoryRuleDecision), specific helpers (defaultFactoryRules({ version, overrides })), and explicit commands are given, but no copy-paste code blocks exist, so it is mostly executable rather than fully copy-paste ready — fits 4 over 5.

4 / 5

Workflow Clarity

Sequenced multi-step processes (find configuration, apply overrides, verify) include explicit validation checkpoints (run narrow Factory rule tests, package typecheck, Web build) and feedback-loop guardrails, matching the 5 anchor.

5 / 5

Progressive Disclosure

A single-purpose, well-sectioned body with clear headers and no nested or buried references; no bundle files are needed and structure is easy to navigate, fitting the 5 anchor for a self-contained skill.

5 / 5

Total

19

/

20

Passed

Description

50%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 is specific and occupies a clear niche, but it is purely a 'what' statement with no 'when to use' trigger guidance and only technical jargon rather than natural trigger terms. Adding a 'Use when...' clause with natural phrasing would raise completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause with natural trigger phrases (e.g., 'Use when changing Factory policy, adding or replacing a rule handler, or applying an exact-leaf override in deployment code').

Include common user-facing synonyms beyond jargon (e.g., 'Factory rules', 'rule overrides', 'deployment policy') so the trigger terms match what a user would actually say.

Keep the concrete action list but expand to the full scope (configure rules, apply exact-leaf overrides, version changes) for fuller specificity coverage.

DimensionReasoningScore

Specificity

Names the domain ('Mastra Factory rules', 'exact-leaf overrides', 'deployment code') and two concrete actions (configure rules, apply overrides), but coverage is not comprehensive — fits the 3 anchor rather than the several-actions 4 anchor.

3 / 5

Completeness

A clear 'what' is stated but no 'Use when...' clause or equivalent trigger guidance exists, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Only domain jargon appears ('Mastra Factory', 'exact-leaf overrides'); no natural user-facing trigger phrases or synonyms are present, so it sits at 2 (jargon-heavy, missing natural phrases) rather than 3.

2 / 5

Distinctiveness Conflict Risk

The description names a very specific niche (typed Mastra Factory rules and exact-leaf overrides in deployment code) with minimal overlap risk, matching the clear-niche 5 anchor.

5 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mastra-ai/mastra
Reviewed

Table of Contents

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.