Use when migrating, restructuring, publishing, or auditing an existing Claude skill into a Tessl tile; converting flat .md files or SKILL.md bundles; fixing Tessl Quality, Impact, Uplift, frontmatter, metadata, tile.json summary, README, markdown reference links, registry-vs-local Quality gaps, artifact anchors, auto-eval wait discipline, or pushing tile scores from 88-99% to 100%.
100
100%
Does it follow best practices?
Impact
100%
1.11xAverage score across 4 eval scenarios
Advisory
Suggest reviewing before use
The platform engineering team has been maintaining a Kubernetes deployment skill as a simple folder with a SKILL.md and supporting reference files. The team has decided to publish it to the Tessl registry so other teams can install and benefit from it. Before it can be published, the skill bundle needs to be restructured to meet Tessl's standards and pass all quality checks.
The existing skill is located at inputs/SKILL.md, with supporting reference files under inputs/references/. A quick review has flagged a few structural issues that need to be resolved before the bundle can be accepted by the registry.
Your job is to take the existing files and produce a corrected, Tessl-ready version of the skill. Do not worry about running any CLI tools — just produce the correct file structure and content that would pass Tessl's validation.
Produce the restructured skill files at the following paths (write them to your working directory):
skills/deploy-kubernetes/SKILL.md — the corrected entry pointskills/deploy-kubernetes/references/phase-1-validate.md — (updated if needed)skills/deploy-kubernetes/references/phase-2-helm.md — (updated if needed)skills/deploy-kubernetes/references/phase-3-rollout.md — (updated if needed)skills/deploy-kubernetes/references/phase-4-checks.md — (updated if needed)tile.json — Tessl tile manifestREADME.md — tile-root readme for the registryWrite a brief migration-notes.md explaining the specific issues you found and what you changed to fix them.