CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

typescript-tooling-migration

Migrate or upgrade TypeScript tooling in the Phoenix monorepo. Use when upgrading TypeScript versions, switching tools (ESLint to oxlint, Prettier to oxfmt), upgrading bundlers (Vite, esbuild), or making major dependency upgrades. Triggers on requests to migrate, upgrade, or replace TypeScript/JavaScript tooling.

70

Quality

88%

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

81%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-executed instruction-only skill: a 12-phase workflow with thorough validation checkpoints, concrete commands, and useful repo-specific structure (monorepo layout, out-of-scope directories, CI map). The main improvement levers are deduplicating the version-alignment rule and moving long-tail troubleshooting detail to reference files.

DimensionReasoningScore

Conciseness

Dense tables and command blocks assume Claude's competence with no concept padding. Minor trimmable redundancy exists: the js/app-vs-root version alignment rule is stated three times (Shared Dependencies table, Phase 12, and 'Keep Packages in Sync'), and the References section includes generic links (pnpm homepage).

4 / 5

Actionability

Concrete executable commands throughout — pnpm add/update/remove with the -w workspace flag, pre-commit hook YAML with real file regexes, cache-clear paths, and a full verification command list. The pervasive <tool>/<version> placeholders are justified for a template-style migration guide, but no fully worked concrete example (e.g., a specific version bump) is shown, keeping it just short of copy-paste-ready.

4 / 5

Workflow Clarity

Twelve clearly sequenced phases with an explicit validation checklist in Phase 10 (typecheck, lint, fmt, unit, build, E2E, pre-commit across both workspaces) and a Troubleshooting section giving per-failure feedback loops (fix cycle, CI-vs-local, config-not-found). The keep-old-tool-until-verified checkpoint is stated for replacements.

5 / 5

Progressive Disclosure

Single-file skill (no bundle files exist) with a well-organized section hierarchy, tables, and navigable headers. All ~360 lines are inline; troubleshooting and per-type workflow details could plausibly be split into one-level-deep reference files, leaving minor organization headroom.

4 / 5

Total

17

/

20

Passed

Description

92%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 description: concrete capabilities with named example tools, explicit trigger clauses, and tight scoping to the Phoenix monorepo. The only gap is a few missing natural synonyms ('update', 'bump') in trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named tools — 'upgrading TypeScript versions', 'switching tools (ESLint to oxlint, Prettier to oxfmt)', 'upgrading bundlers (Vite, esbuild)', 'making major dependency upgrades' — giving comprehensive coverage of the domain.

5 / 5

Completeness

Explicitly answers both 'what' ('Migrate or upgrade TypeScript tooling in the Phoenix monorepo') and 'when' ('Use when upgrading... Triggers on requests to migrate, upgrade, or replace') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage — 'migrate', 'upgrade', 'replace TypeScript/JavaScript tooling' plus specific tool names (ESLint, oxlint, Prettier, oxfmt, Vite, esbuild) — but misses common variations users might say such as 'update', 'bump versions', or file extensions.

4 / 5

Distinctiveness Conflict Risk

Clear niche scoped to a named monorepo and a specific tool ecosystem (TypeScript tooling migrations); unlikely to trigger for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 2 missing, 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

Arize-ai/phoenix

Path

.agents/skills/typescript-tooling-migration/SKILL.md

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.