compiler-port

Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./compiler/.claude/skills/compiler-port/SKILL.md

Quality

Content

92%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 tight, well-structured end-to-end workflow with concrete paths, explicit validation checkpoints, and a working feedback loop. The only minor gap is that some execution detail is delegated to the port-pass agent prompt rather than inlined.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: dense mapping table, concrete file paths, and no padding or restating of known concepts.	5 / 5
Actionability	Concrete file paths, an explicit test command, and subagent wiring make guidance mostly executable, though some detail is delegated to the port-pass agent prompt rather than stated inline.	4 / 5
Workflow Clarity	Steps 0-6 are clearly sequenced with explicit validation checkpoints (validate pass name, check already-ported) and a review->fix->re-test feedback loop in Step 5 until clean.	5 / 5
Progressive Disclosure	Well-organized sections with one-level-deep delegation to a subagent and external scripts/reviews; content is appropriately split and easy to navigate.	5 / 5
	Total	19 / 20 Passed

Description

63%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 and specifically conveys what the skill does but omits any explicit trigger guidance for when Claude should invoke it, which caps completeness. Adding a 'Use when...' clause would meaningfully raise the score.

Suggestions

Add an explicit trigger clause such as 'Use when porting a React Compiler pass from TypeScript to Rust' to satisfy the 'when' half of completeness.

Include natural synonyms and concrete trigger phrasing users might say (e.g., 'port a compiler pass', 'translate pass to Rust', 'HIR/reactive pass port') to improve trigger term quality.

Keep the current concrete action list but front-load a short trigger phrase so the description answers 'what' and 'when' up front.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions ('Gathers context, plans the port, implements... with test-fix loop, then reviews'), giving comprehensive coverage of the workflow.	5 / 5
Completeness	It clearly states what the skill does but provides no explicit 'when to use it' clause; per the rubric, a missing 'Use when...' caps completeness at 3.	3 / 5
Trigger Term Quality	Domain terms like 'compiler pass', 'TypeScript to Rust', and 'port' are present but it lacks natural user-facing trigger phrases and synonyms; no 'Use when...' guidance.	3 / 5
Distinctiveness Conflict Risk	The TS-to-Rust compiler-pass niche is quite specific and unlikely to trigger for unrelated skills, with only minor overlap risk against general porting skills.	4 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

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: facebook/react
Path: compiler/.claude/skills/compiler-port/SKILL.md
Commit: 7c6ac13

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.