CtrlK
BlogDocsLog inGet started
Tessl Logo

migrate-to-factory

Migrates user-specified skills and their supporting scripts, references, assets, and workflow instructions into an existing Warp Factory configuration repository. Use when a user asks to port or adapt an existing agent workflow into Factory agents and skills. Do not use for routine Factory-file edits or for registering or operating a live Factory.

71

Quality

86%

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

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.

A well-structured, concise instruction skill with a clear validated workflow and appropriate deference to the factory-files skill for syntax. The only trim opportunity is minor redundancy around source-file read-only handling.

DimensionReasoningScore

Conciseness

The ~38-line body is lean, defers schema detail to the factory-files skill and external docs, and avoids explaining concepts Claude already knows; a small redundancy between 'read-only inputs' and the closing 'do not modify source files' line keeps it just below fully lean.

4 / 5

Actionability

Concrete placement rules (skills/<name>/, agents/<agent-name>/skills/<name>/) and named files to read give mostly executable guidance; it deliberately defers exact syntax to factory-files, leaving minor gaps.

4 / 5

Workflow Clarity

A clear 5-step sequence includes an explicit validation step ('Use factory-files to validate... Fix all reported diagnostics') and a stop-and-ask conflict gate, providing a feedback loop for a repository-editing operation.

5 / 5

Progressive Disclosure

Under 50 lines with no bundle files, organized into clear Scope and Workflow sections and pointing out to the factory-files skill and external docs; this meets the simple-skill exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

87%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.

A strong, third-person description that states concrete capabilities, gives an explicit trigger phrase, and adds a negative boundary to reduce misfires. The only weakness is single-verb action coverage rather than multiple distinct verbs.

DimensionReasoningScore

Specificity

Names several specific objects migrated (skills, scripts, references, assets, workflow instructions) into a Factory repository, but uses a single action verb rather than multiple distinct concrete actions, so it sits below the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both what (migrates skills and supporting resources into a Factory config repo) and when (concrete 'Use when...' trigger phrase), plus a negative boundary clause.

5 / 5

Trigger Term Quality

The 'Use when a user asks to port or adapt an existing agent workflow into Factory agents and skills' clause provides good natural keywords, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (porting agent workflows into Factory) paired with an explicit 'Do not use for routine Factory-file edits or for registering or operating a live Factory' boundary minimizes conflict with adjacent skills.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
warpdotdev/common-skills
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.