Write a Tessl Migration Runbook for the Platform Team

Background

A mid-size engineering company has a library of 40+ internal Claude skills scattered across various repos as standalone .md files. The developer experience team wants to migrate all of them to the Tessl registry so teams can discover, install, and benefit from version-controlled, eval-backed skills.

Before kicking off the migration work, the team's lead engineer wants a detailed migration runbook that any engineer on the team can follow. The runbook must cover everything from verifying the environment is ready, through the multi-phase migration workflow, to the final publish. It should be opinionated about ordering and flag the common pitfalls that waste time when hit mid-migration.

You have access to the relevant Tessl migration skill. Produce the runbook based on the migration workflow it describes.

Output Specification

Write a single file called migration-runbook.md that covers:

1. Prerequisites checklist — what to verify before touching any skill files
2. Migration phases overview — a brief summary of each phase and what it produces
3. Default configuration — the standard values to use when not otherwise specified (visibility, version, eval agent, etc.)
4. Common pitfalls — the top time-sink mistakes to avoid, with the fix for each
5. Stop conditions — when to pause and report to a human instead of continuing

The runbook should be actionable enough that an engineer who has never run a Tessl migration before can follow it end-to-end.