CtrlK
BlogDocsLog inGet started
Tessl Logo

factory-plan

Produce a phased implementation plan for a Factory work item, then advance it to execute

60

Quality

69%

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

Quality

Content

85%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 tightly written, actionable orchestration skill with a clear phased workflow and explicit validation and retry checkpoints. Its only weaknesses are mild redundancy and the absence of a concrete transition call shape.

DimensionReasoningScore

Conciseness

The body is lean, directive, and assumes Claude's competence without explaining known concepts; minor redundancy between the phases and the Behavior Rules (e.g., 'record decisions as assumptions' restated) keeps it just below a clean 5.

4 / 5

Actionability

Provides concrete, executable directives tied to specific tooling and parameters (factory_transition_work_item, stage: "execute", rationale max 1000 chars, .artifacts/plans/issue-<number>.md), with only minor gaps in giving the exact transition call shape.

4 / 5

Workflow Clarity

A clear four-phase sequence (Verify, Design, Write Plan, Transition) with explicit validation checkpoints and a concrete rejection feedback loop ('read the stated reason, address it... and retry once corrected').

5 / 5

Progressive Disclosure

Single-purpose skill under ~50 lines with no need for external references; content is cleanly sectioned into phases and behavior rules with the one output path clearly signaled, meeting the well-organized-sections exception.

5 / 5

Total

18

/

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 states what the skill does but omits any 'when to use it' trigger guidance, capping completeness at 3. It is reasonably distinct and specific but relies on platform jargon over natural user phrasing.

Suggestions

Append a 'Use when...' clause naming natural user triggers, e.g. 'Use when the user asks to plan or stage a Factory work item for execution.'

Add natural synonyms or phrasings a user might actually say (e.g. 'plan a Factory work item', 'move a work item to execute') to improve trigger term quality.

DimensionReasoningScore

Specificity

Names the domain ('Factory work item') and two concrete actions ('Produce a phased implementation plan', 'advance it to execute'), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Has a clear 'what' but the 'when' is entirely missing with no 'Use when...' clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Contains domain keywords ('phased implementation plan', 'Factory work item', 'execute') but these are platform jargon rather than natural user phrasings, and no synonyms or 'Use when' trigger is present.

3 / 5

Distinctiveness Conflict Risk

Tied to a specific Factory workflow niche (planning-to-execute transition), mostly distinct with only minor overlap risk against the closely related triage skill, but lacks explicit trigger phrases that would minimize conflict risk.

4 / 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.